SALT-PEPPER(1)

πŸ“¦
version 0.5.5 Β· 3 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble

✨ 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 the PEPPERRC environment 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 the jobs.list_jobs runner 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 to https://localhost:8080 🏠
  • -a EAUTH, --auth=EAUTH, --eauth=EAUTH, --extended-auth=EAUTH β€” specify the external_auth backend 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 --noninteractive here and --non-interactive up 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 the token_expire_user_override Master 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 /token and send commands through the /run URL instead of the traditional session token approach. different route, same destination πŸ›£οΈ
  • -x CACHE β€” cache file location. default is a file path in the PEPPERCACHE environment 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