golden hour

/opt/saltstack/salt/lib/python3.10/site-packages/salt/runners/__pycache__

File/Folder	Size	Actions
__init__.cpython-310.pyc	197 B
asam.cpython-310.pyc	7.9 KB
auth.cpython-310.pyc	1.89 KB
bgp.cpython-310.pyc	12.55 KB
cache.cpython-310.pyc	10.98 KB
cloud.cpython-310.pyc	4.16 KB
config.cpython-310.pyc	1.08 KB
ddns.cpython-310.pyc	6.7 KB
digicertapi.cpython-310.pyc	16.23 KB
doc.cpython-310.pyc	1.76 KB
drac.cpython-310.pyc	4.15 KB
error.cpython-310.pyc	771 B
event.cpython-310.pyc	2.32 KB
f5.cpython-310.pyc	8.29 KB
fileserver.cpython-310.pyc	17.12 KB
git_pillar.cpython-310.pyc	3.54 KB
http.cpython-310.pyc	2.55 KB
jobs.cpython-310.pyc	13.26 KB
launchd.cpython-310.pyc	1.49 KB
lxc.cpython-310.pyc	13.3 KB
manage.cpython-310.pyc	21.71 KB
mattermost.cpython-310.pyc	4.21 KB
mine.cpython-310.pyc	1.79 KB
nacl.cpython-310.pyc	8.46 KB
net.cpython-310.pyc	27.7 KB
network.cpython-310.pyc	2.59 KB
pagerduty.cpython-310.pyc	3.96 KB
pillar.cpython-310.pyc	4.25 KB
pkg.cpython-310.pyc	1.37 KB
queue.cpython-310.pyc	8.14 KB
reactor.cpython-310.pyc	4.32 KB
salt.cpython-310.pyc	4.58 KB
saltutil.cpython-310.pyc	15.88 KB
sdb.cpython-310.pyc	2.54 KB
smartos_vmadm.cpython-310.pyc	7.99 KB
spacewalk.cpython-310.pyc	7.54 KB
ssh.cpython-310.pyc	1000 B
state.cpython-310.pyc	8.22 KB
survey.cpython-310.pyc	5.07 KB
test.cpython-310.pyc	2.65 KB
thin.cpython-310.pyc	1.81 KB
vault.cpython-310.pyc	10.01 KB
venafiapi.cpython-310.pyc	5.57 KB
virt.cpython-310.pyc	13.15 KB
vistara.cpython-310.pyc	4.39 KB
winrepo.cpython-310.pyc	5.14 KB

Edit: salt.cpython-310.pyc

�����xe�����������������������@���sl���d�Z�ddlZddlZddlZddlZddlZddlZddlm	Z	�e�
e�Zdd��Z
						dd	d
�ZdS�)a���
This runner makes Salt's
execution modules available
on the salt master.

.. versionadded:: 2016.11.0

.. _salt_salt_runner:

Salt's execution modules are normally available
on the salt minion. Use this runner to call
execution modules on the salt master.
Salt :ref:`execution modules <writing-execution-modules>`
are the functions called by the ``salt`` command.

Execution modules can be called with ``salt-run``:

.. code-block:: bash

salt-run salt.cmd test.ping
    # call functions with arguments and keyword arguments
    salt-run salt.cmd test.arg 1 2 3 key=value a=1

Execution modules are also available to salt runners:

.. code-block:: python

__salt__['salt.cmd'](fun=fun, args=args, kwargs=kwargs)

�����N)�SaltClientErrorc�����������������O���s����t��d|���tjjjd
i�|��}|�dd�}t�t	�}tj
�|�|d<�|r>tjj
||d�|d�|d�|�d�d����|d	<�ni�|d	<�tj
j|tj
�|�td
�}|�|v�r\||��|i�|��S�d�|��S�)a���
    .. versionchanged:: 2018.3.0
        Added ``with_pillar`` argument

Execute ``fun`` with the given ``args`` and ``kwargs``.  Parameter ``fun``
    should be the string :ref:`name <all-salt.modules>` of the execution module
    to call.

.. note::
        Execution modules will be loaded *every time* this function is called.
        Additionally, keep in mind that since runners execute on the master,
        custom execution modules will need to be synced to the master using
        :py:func:`salt-run saltutil.sync_modules
        <salt.runners.saltutil.sync_modules>`, otherwise they will not be
        available.

with_pillar : False
        If ``True``, pillar data will be compiled for the master

.. note::
            To target the master in the pillar top file, keep in mind that the
            default ``id`` for the master is ``<hostname>_master``. This can be
            overridden by setting an ``id`` configuration parameter in the
            master config file.

CLI Example:

.. code-block:: bash

salt-run salt.cmd test.ping
        # call functions with arguments and keyword arguments
        salt-run salt.cmd test.arg 1 2 3 a=1
        salt-run salt.cmd mymod.myfunc with_pillar=True
    z.Called salt.cmd runner with minion function %s�with_pillarF�grains�id�saltenv�	pillarenv)r���r����pillar)�utils�contextz'{}' is not available.N��)�log�debug�saltr	����argsZclean_kwargs�pop�copy�deepcopy�__opts__�loaderr���r���Z
get_pillar�getZcompile_pillarZminion_mods�__context__�format)�funr����kwargsr����optsZ	functionsr���r����E/opt/saltstack/salt/lib/python3.10/site-packages/salt/runners/salt.py�cmd,���s0���#
������r���r����glob��c�����������������K���s����t�j�td���G}	z|	j|�|f||ptd�||||d�|��W�W��d����S��tyN�}
�zt�d||�|��t�|
��i�W��Y�d}
~
W��d����S�d}
~
ww�1�sRw���Y��dS�)a���
    .. versionadded:: 2017.7.0

Execute ``fun`` on all minions matched by ``tgt`` and ``tgt_type``.
    Parameter ``fun`` is the name of execution module function to call.

This function should mainly be used as a helper for runner modules,
    in order to avoid redundant code.
    For example, when inside a runner one needs to execute a certain function
    on arbitrary groups of minions, only has to:

.. code-block:: python

ret1 = __salt__['salt.execute']('*', 'mod.fun')
        ret2 = __salt__['salt.execute']('my_nodegroup', 'mod2.fun2', tgt_type='nodegroup')

It can also be used to schedule jobs directly on the master, for example:

.. code-block:: yaml

schedule:
            collect_bgp_stats:
                function: salt.execute
                args:
                    - edge-routers
                    - bgp.neighbors
                kwargs:
                    tgt_type: nodegroup
                days: 1
                returner: redis
    Z	conf_file�timeout)�argr����tgt_type�ret�jid�kwargNz#Error while executing %s on %s (%s))r����clientZget_local_clientr���r���r���r����error)Ztgtr���r ���r���r!���r"���r#���r$���r���r%���Zclient_errorr���r���r����executem���s0���*�
�	��

��
�r'���)r���Nr���r���r���N)�__doc__r���ZloggingZsalt.clientr���Zsalt.loaderZsalt.pillarZsalt.utils.argsZsalt.exceptionsr���Z	getLogger�__name__r���r���r'���r���r���r���r����<module>���s"����
D�