You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the salt.local action is called from the command line providing module=state.highstate and target, the high state is applied to the target machine. If the action is trigger via the action-alias, the result appears to apply the configuration changes but none are observred on the target machine. It seems like it's running with test=true.
When the
salt.local
action is called from the command line providingmodule=state.highstate
andtarget
, the high state is applied to the target machine. If the action is trigger via the action-alias, the result appears to apply the configuration changes but none are observred on the target machine. It seems like it's running withtest=true
.salt.local from action-alias
salt.local from cli
The only difference I can see between the 2 calls is that
arg
parameter is passed an empty list. This behaviour has been observed using salt-2018.3.4The text was updated successfully, but these errors were encountered: