Configure the CLI

Store non-secret defaults with quollvault config; keep the bearer token only in the environment.

quollvault config set api https://api.quollvault.com
quollvault config set app <app-uuid>
quollvault config set environment <environment-uuid>
quollvault config show
export QUOLLVAULT_TOKEN='<automation-token>'

The API URL must be an HTTPS origin for remote hosts. App and Environment values are canonical UUIDv4 IDs, not names.

Expected result

Commands use configured defaults unless an explicit command option overrides the App/Environment.

Prompt an agent to configure the CLI

Configure the QuollVault CLI for this project without exposing secrets.

Inspect the repository and existing QuollVault configuration first. Set the API origin to `https://api.quollvault.com`, then configure the target App UUID and Environment UUID with `quollvault config set`. Keep the Automation Token only in `QUOLLVAULT_TOKEN` for the active shell or the CI secret store; never put it in a config file, command argument, source file or log. Confirm the resulting non-secret settings with `quollvault config show`.

If the App or Environment is not unambiguously known, ask me which existing QuollVault App and Environment to target before writing configuration. If there are several safe ways to supply the token for this workflow, ask which secret-management approach I prefer. Do not invent UUIDs or use names in place of UUIDs.

Make only the configuration changes needed for this task and report the selected non-secret target values.

Common failures

• Configure api first: set api.
• missing token: set QUOLLVAULT_TOKEN in the process/CI secret store.
• authorization failure: verify the token is active and scoped to the selected App.

Related

• Automation Tokens
• Environment variables