salt-ssh
¶salt-ssh '*' [ options ] sys.doc
salt-ssh -E '.*' [ options ] sys.doc cmd
Salt SSH allows for salt routines to be executed using only SSH for transport
Print the version of Salt that is running.
Show program's dependencies and version number, and then exit
Show the help message and exit
The location of the Salt configuration directory. This directory contains
the configuration files for Salt master and minions. The default location
on most systems is /etc/salt
.
Raise any original exception rather than exiting gracefully. Default: False.
Execute a raw shell command.
Define which roster system to use, this defines if a database backend, scanner, or custom roster system is used. Default is the flat file roster.
Define an alternative location for the default roster file location. The
default roster file is called roster
and is found in the same directory
as the master config file.
New in version 2014.1.0.
Force a refresh of the master side data cache of the target's data. This is needed if a target's grains have been changed and the auto refresh timeframe has not been reached.
Set the number of concurrent minions to communicate with. This value defines how many processes are opened up at a time to manage connections, the more running process the faster communication should be, default is 25.
Pass in extra files to include in the state tarball.
One or comma-separated list of extra Python modulesto be included into Minimal Salt.
One or comma-separated list of extra Python modulesto be included into Thin Salt.
Turn on command verbosity, display jid.
Return the data from minions as a group after they all return.
Remove the deployment of the salt files when done executing.
Select a random temp dir to deploy on the remote system. The dir will be cleaned after the execution.
Trigger a thin tarball regeneration. This is needed if custom grains/modules/states have been added or updated.
Path to a python2 binary which has salt installed.
Path to a python3 binary which has salt installed.
Pass a JID to be used instead of generating one.
Run the ssh_pre_flight script defined in the roster. By default this script will only run if the thin dir does not exist on the target minion. This option will force the script to run regardless of the thin dir existing or not.
Specify the SSH private key file to be used for authentication.
Specify the SSH private key file's passphrase if need be.
By default ssh host keys are honored and connections will ask for approval. Use this option to disable StrictHostKeyChecking.
Fully ignores ssh host keys which by default are honored and connections would ask for approval. Useful if the host key of a remote server has changed and would still error with --ignore-host-keys.
Set the default user to attempt to use when authenticating.
Set the default password to attempt to use when authenticating.
Interactively ask for the SSH password with no echo - avoids password in process args and stored in history.
Set this flag to attempt to deploy the authorized ssh key with all minions. This combined with --passwd can make initial deployment of keys very fast and easy.
Use the only authentication identity files configured in the ssh_config files. See IdentitiesOnly flag in man ssh_config.
Run command via sudo.
Comma-separated list of ports to scan in the scan roster.
Scanning socket timeout for the scan roster.
Logging options which override any settings defined on the configuration files.
Console logging log level. One of all
, garbage
, trace
,
debug
, info
, warning
, error
, quiet
. Default:
warning
.
Log file path. Default: /var/log/salt/ssh.
Logfile logging log level. One of all
, garbage
, trace
,
debug
, info
, warning
, error
, quiet
. Default:
warning
.
The default matching that Salt utilizes is shell-style globbing around the minion id. See https://docs.python.org/3/library/fnmatch.html#module-fnmatch.
The target expression will be interpreted as a PCRE regular expression rather than a shell glob.
Pass in an alternative outputter to display the return of data. This outputter can be any of the available outputters:
highstate
,json
,key
,overstatestage
,pprint
,raw
,txt
,yaml
, and many others.
Some outputters are formatted only for data returned from specific functions.
If an outputter is used that does not support the data passed into it, then
Salt will fall back on the pprint
outputter and display the return data
using the Python pprint
standard library module.
Print the output indented by the provided value in spaces. Negative values disable indentation. Only applicable in outputters that support indentation.
Write the output to the specified file.
Append the output to the specified file.
Disable all colored output
Force colored output
Note
When using colored output the color codes are as follows:
green
denotes success, red
denotes failure, blue
denotes
changes and success and yellow
denotes a expected future change in configuration.
Override the configured state_output value for minion output. One of 'full', 'terse', 'mixed', 'changes' or 'filter'. Default: 'none'.
Override the configured state_verbose value for minion output. Set to True or False. Default: none.
Note
If using --out=json
, you will probably want --static
as well.
Without the static option, you will get a separate JSON string per minion
which makes JSON output invalid as a whole.
This is due to using an iterative outputter. So if you want to feed it
to a JSON parser, use --static
as well.
salt(7) salt-master(1) salt-minion(1)