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: event.cpython-310.pyc

�����xec����������������������@���s,���d�Z�ddlZddlZe�e�Zddd�ZdS�)zQ
Module for sending events using the runner system.

.. versionadded:: 2016.11.0
�����Nc�����������������C���s,���|pi�}t�jjjttd�dd�}|�||��S�)a���
    Send an event with the given tag and data.

This is useful for sending events directly to the master from the shell
    with salt-run. It is also quite useful for sending events in orchestration
    states where the ``fire_event`` requisite isn't sufficient because it does
    not support sending custom data with the event.

Note that event tags will *not* be namespaced like events sent with the
    ``fire_event`` requisite! Whereas events produced from ``fire_event`` are
    prefixed with ``salt/state_result/<jid>/<minion_id>/<name>``, events sent
    using this runner module will have no such prefix. Make sure your reactors
    don't expect a prefix!

:param tag: the tag to send with the event
    :param data: an optional dictionary of data to send with the event

CLI Example:

.. code-block:: bash

salt-run event.send my/custom/event '{"foo": "bar"}'

Orchestration Example:

.. code-block:: yaml

# orch/command.sls

run_a_command:
          salt.function:
            - name: cmd.run
            - tgt: my_minion
            - arg:
              - exit {{ pillar['exit_code'] }}

send_success_event:
          salt.runner:
            - name: event.send
            - tag: my_event/success
            - data:
                foo: bar
            - require:
              - salt: run_a_command

send_failure_event:
          salt.runner:
            - name: event.send
            - tag: my_event/failure
            - data:
                baz: qux
            - onfail:
              - salt: run_a_command

.. code-block:: bash

salt-run state.orchestrate orch.command pillar='{"exit_code": 0}'
        salt-run state.orchestrate orch.command pillar='{"exit_code": 1}'
    Zsock_dirF)�listen)�salt�utils�eventZget_master_eventZ__opts__Z
fire_event)�tag�datar�����r����F/opt/saltstack/salt/lib/python3.10/site-packages/salt/runners/event.py�send���s
���<
�r
���)N)�__doc__ZloggingZsalt.utils.eventr���Z	getLogger�__name__�logr
���r���r���r���r	����<module>���s
����