AppBarn Docs

Appearance

Configure the CLI ​

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

sh
appbarn config set api https://api.app-barn.com
appbarn config set app <app-uuid>
appbarn config set environment <environment-uuid>
appbarn config show
export APPBARN_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
text
Configure the AppBarn CLI for this project without exposing secrets.

Inspect the repository and existing AppBarn configuration first. Set the API origin to `https://api.app-barn.com`, then configure the target App UUID and Environment UUID with `appbarn config set`. Keep the Automation Token only in `APPBARN_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 `appbarn config show`.

If the App or Environment is not unambiguously known, ask me which existing AppBarn 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 APPBARN_TOKEN in the process/CI secret store.
  • authorization failure: verify the token is active and scoped to the selected App.