capy connect: Link a Credential Provider

Synopsis

capy connect
capy connect <provider>
capy connect <provider> --var API_KEY

Description

With no provider, capy connect lists available integrations. With a provider, it links an existing environment variable so capy rotate can manage that credential. Some provider integrations support importing or discovering values instead; their exact options depend on the provider. The default provider mode is test; pass --live for live mode. Capy syncs a successful link unless --no-push is supplied. It requires a project with an active branch and is unavailable in local-only mode.

Flags

Flag	Description
`--live`	Use live mode instead of test mode.
`--var <name>`	Name the existing variable to link.
`--account <id>`	Select a provider account when more than one is available.
`--no-push`	Record the link locally without syncing it.
`--non-tty`	Never prompt; resolve available choices from flags or fail.
`--reauth`	Reauthenticate with the provider.
`--json`	Emit machine-readable output for supported import integrations.
`--dry-run`	Preview supported Dokploy import or discovery work without writing or pushing.
`--discover`	For Dokploy, discover matching services under the current repository.
`-y, --yes`	Skip the Dokploy import or discovery confirmation.
`--overwrite`	For Dokploy import, make the branch match Dokploy’s variable set exactly.
`--environment <names>`	For Dokploy discovery, limit environments with a comma-separated list.

Dokploy import options are --base-url <url>, --application <id>, --compose <id>, and --token-env <name>. --application and --compose are mutually exclusive.

Getting started

Using Capy

Deploying

Organizations

Branches

Team

CLI reference

Under the hood

Comparisons

capy connect: Link a Credential Provider

Synopsis

Description

Flags

See also

​Synopsis

​Description

​Flags

​See also

Synopsis

Description

Flags

See also