SALT-PEPPER(1)
β¨ SALT-PEPPER(1) β¨
okay bestie, pull up a chair π«Ά this is the salt-pepper manual page β it lives in the User Commands section, and it's your lil backstage pass to a remote salt-api instance. let's get into it π
πΈ NAME πΈ
salt-pepper β the tool you use to access a salt-api instance β¨
π SYNOPSIS π
salt-pepper [opts]
π¦ DESCRIPTION π¦
it's a CLI interface to a remote salt-api instance. that's the whole vibe. you talk, salt listens π
π OPTIONS π
--versionβ show the program's version number and then dip out. bye π-h,--helpβ show this help message and exit. the classic.-c CONFIGβ where your config file lives. the default is a file path that's sitting in thePEPPERRCenvironment variable, or else~/.pepperrc. π-vβ bump up output verbosity. you can stack this one multiple times if you're feeling extra π-H,--debug-httpβ dumps the HTTP request/response headers out on stderr. great for snooping fr fr π--ignore-ssl-errorsβ ignore any SSL certificate that may be encountered.
β οΈ ngl bestie, it is recommended to resolve certificate errors for production. don't be out here ignoring certs in prod, that's not the move π
Pepper salt Options:
Mimic the salt CLI π«
-t TIMEOUT,--timeout=TIMEOUTβ how long to wait (in seconds) before handing control back to your shell. patience is a virtue but also a config value β³--client=CLIENTβ pick which salt-api client to use (local,local_async,runner, etc). choose your fighter π₯--json=JSON_INPUTβ type JSON straight at the CLI instead of using positional (text) arguments. this is so useful when your args need complex data structures. heads up tho: specifying this argument makes your positional arguments get ignored entirely. so like. pick one π--json-file=JSON_FILEβ point at a file containing the JSON that salt-pepper should use π--fail-if-incompleteβ returns a failure exit code if not all minions respond. this option requires that the authenticated user has access to run thejobs.list_jobsrunner function. no access, no dice π²
Targeting Options:
Target which minions to run commands on π―
-E,--pcreβ target hostnames using PCRE regular expressions. regex girlies rise π-L,--listβ specify a comma delimited list of hostnames βοΈ-G,--grainβ target based on system properties πΎ--grain-pcreβ target based on PCRE matches on system properties π-I,--pillarβ target based on pillar values ποΈ--pillar-pcreβ target based on PCRE matches on pillar values π-R,--rangeβ target based on a range expression π-C,--compoundβ target based on a compound expression π§ͺ-N,--nodegroupβ target based on a named nodegroup π―--batch=BATCHβ (the original page leaves this one blank bestie, so we leave it blank too. mysterious. iconic. main character energy honestly π )
Authentication Options:
Authentication credentials can optionally be supplied via these environment variables: SALTAPI_URL, SALTAPI_USER, SALTAPI_PASS, SALTAPI_EAUTH. env vars doing the most, as always π
-u SALTAPIURL,--saltapi-url=SALTAPIURLβ specify the host url. defaults tohttps://localhost:8080π-a EAUTH,--auth=EAUTH,--eauth=EAUTH,--extended-auth=EAUTHβ specify theexternal_authbackend to authenticate against, and it'll interactively prompt you for credentials. four whole names for one option, she contains multitudes β¨--username=USERNAMEβ optional, defaults to user name. it'll be prompted if empty, unless you passed--non-interactiveπ--password=PASSWORDβ optional, but it will be prompted unless--noninteractiveπ
π yes bestie, the original page really does spell it--noninteractivehere and--non-interactiveup above. we don't fix it, we respect it. copy the spelling exactly or you'll be sad.
--token-expire=TOKEN_EXPIREβ set eauth token expiry in seconds. must be allowed per user. see thetoken_expire_user_overrideMaster setting for more info. permission check first, always π--non-interactiveβ optional. fail rather than waiting for input. no waiting around, we're busy πβοΈ-T,--make-tokenβ generate and save an authentication token for re-use. the token is generated and made available for the period defined in the Salt Master. set it and forget it (until the Master says otherwise) ποΈ-r,--run-uriβ use an eauth token from/tokenand send commands through the/runURL instead of the traditional session token approach. different route, same destination π£οΈ-x CACHEβ cache file location. default is a file path in thePEPPERCACHEenvironment variable, or~/.peppercache. ποΈ
π SEE ALSO π
the full documentation for salt-pepper is maintained as a Texinfo manual. if the info and salt-pepper programs are properly installed at your site, then this command:
info salt-pepper
should give you access to the complete manual. go read, bestie, it's giving educated πβ¨
that's the whole page!! this is salt-pepper 0.5.5-1, dated March 2018 π slay, mwah, go pepper some salt π«Άπ
π¦ where this page comes from
- debian bookworm: salt-pepper 0.5.5-1 Β· Apache-2.0
- debian trixie: salt-pepper 0.5.5-1 Β· Apache-2.0
- ubuntu jammy: salt-pepper 0.5.5-1 Β· Apache-2.0
- ubuntu noble: salt-pepper 0.5.5-1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms