These events are fired on the Salt Master event bus. This list is not comprehensive.
salt/auth
Fired when a minion performs an authentication check with the master.
Variables: |
|
---|
Note
Minions fire auth events on fairly regular basis for a number
of reasons. Writing reactors to respond to events through
the auth cycle can lead to infinite reactor event loops
(minion tries to auth, reactor responds by doing something
that generates another auth event, minion sends auth event,
etc.). Consider reacting to salt/key
or salt/minion/<MID>/start
or firing a custom event tag instead.
salt/minion/<MID>/start
Fired every time a minion connects to the Salt master.
Variables: | id -- The minion ID. |
---|
salt/key
Fired when accepting and rejecting minions keys on the Salt master.
Variables: |
|
---|
Warning
If a master is in auto_accept mode
, salt/key
events
will not be fired when the keys are accepted. In addition, pre-seeding
keys (like happens through Salt-Cloud) will not cause
firing of these events.
salt/job/<JID>/new
Fired as a new job is sent out to minions.
Variables: |
|
---|
salt/job/<JID>/ret/<MID>
Fired each time a minion returns data for a job.
Variables: |
|
---|
salt/job/<JID>/prog/<MID>/<RUN NUM>
Fired each time a each function in a state run completes execution. Must be
enabled using the state_events
option.
Variables: |
|
---|
salt/presence/present
Events fired on a regular interval about currently connected, newly
connected, or recently disconnected minions. Requires the
presence_events
setting to be enabled.
Variables: | present -- A list of minions that are currently connected to the Salt master. |
---|
salt/presence/change
Fired when the Presence system detects new minions connect or disconnect.
Variables: |
|
---|
Unlike other Master events, salt-cloud
events are not fired on behalf of a
Salt Minion. Instead, salt-cloud
events are fired on behalf of a VM. This
is because the minion-to-be may not yet exist to fire events to or also may have
been destroyed.
This behavior is reflected by the name
variable in the event data for
salt-cloud
events as compared to the id
variable for Salt
Minion-triggered events.
salt/cloud/<VM NAME>/creating
Fired when salt-cloud starts the VM creation process.
Variables: |
|
---|
salt/cloud/<VM NAME>/deploying
Fired when the VM is available and salt-cloud begins deploying Salt to the new VM.
Variables: |
|
---|
salt/cloud/<VM NAME>/requesting
Fired when salt-cloud sends the request to create a new VM.
Variables: |
|
---|
salt/cloud/<VM NAME>/querying
Fired when salt-cloud queries data for a new instance.
Variables: |
|
---|
salt/cloud/<VM NAME>/tagging
Fired when salt-cloud tags a new instance.
Variables: |
|
---|
salt/cloud/<VM NAME>/waiting_for_ssh
Fired while the salt-cloud deploy process is waiting for ssh to become available on the new instance.
Variables: |
|
---|
salt/cloud/<VM NAME>/deploy_script
Fired once the deploy script is finished.
Variables: | event -- description of the event. |
---|
salt/cloud/<VM NAME>/created
Fired once the new instance has been fully created.
Variables: |
|
---|
salt/cloud/<VM NAME>/destroying
Fired when salt-cloud requests the destruction of an instance.
Variables: |
|
---|
salt/cloud/<VM NAME>/destroyed
Fired when an instance has been destroyed.
Variables: |
|
---|