CLI configuration
Server and TLS settings
pyplines config set server https://pyplines.example.com
pyplines config set tls.ca_file /absolute/path/company-ca.pem
pyplines config get tls.ca_file
pyplines config show
server and tls.ca_file are the supported configuration keys. config unset KEY removes a saved value. An additional CA supplements system trust; TLS and hostname verification remain enabled.
The operator CLI and API client use system trust. If your server certificate is issued by a trusted CA, no CA override is needed.
Precedence
| Value | Order, highest priority first |
|---|---|
| Server for API requests | Global --server, PYPLINES_SERVER, saved server |
| Token | PYPLINES_TOKEN, saved session for the selected server |
| Additional CA | PYPLINES_CA_FILE, saved tls.ca_file |
| Configuration directory | PYPLINES_CONFIG_DIR, otherwise ~/.pyplines |
login URL explicitly selects and saves its supplied server. For automation, inject PYPLINES_SERVER and PYPLINES_TOKEN through your existing credential delivery system. Do not put tokens into Definitions or commit them alongside configuration.
Session storage
Settings are stored in config.json; tokens are stored separately in sessions.json, keyed by server URL. Passwords are not saved. Tokens are stored unencrypted. On Unix, the directory has mode 0700 and files 0600; on Windows they inherit the user profile's access controls. Exclude sessions from shared backups.
logout attempts server revocation and removes the local token even if that server is unreachable. A token supplied through PYPLINES_TOKEN remains in its external source until you remove or replace it there.
Older settings at ~/.config/pyplines/config.json remain readable until configuration is saved at the new location. Earlier ca_file settings are interpreted as tls.ca_file. Old keychain sessions are no longer read; log in again to create a file-based session.