Skip to main content
This page is the command reference. For the full integration guide — plugin examples for GitHub Actions and Buildkite, AWS credential options, and exit codes — see CI/CD Integration.

​
Overview

The fjall ci command family covers everything a pipeline needs: scaffolding the workflow file (setup), proving the credential works before the first run (verify, status), managing CI deploy tokens (token), and the single non-interactive entry point both official plugins invoke under the hood (run). Pipelines authenticate with a CI deploy token (fjall_dk_), minted in the web app under Settings → CI/CD Tokens and stored as the FJALL_API_KEY secret. Minting is session-only — the CLI cannot create one — but everything after the mint works from the CLI.

​
Subcommands

​
Set up a pipeline

Detects your CI provider and application, resolves the deploy target, and writes the plugin-form workflow file for GitHub Actions or Buildkite.
Without --plan, setup attempts to mint the deploy token before it writes anything — and the API only permits minting from an interactive browser session, so the command fails with guidance and writes no workflow file. Mint the token in the web app (Settings → CI/CD Tokens) and copy the workflow YAML from the CI/CD Integration examples.

​
Verify readiness

Dry-runs the auth handshake before your first pipeline run: credential, principal kind, expiry runway, and (with --app) that the application resolves. Each failing check prints a directional fix.

​
Check token readiness

Summarises your CI deploy credentials: how many tokens exist, which are expiring or expired, and what kind of credential the current session holds.

​
Manage tokens

fjall ci token create exists for completeness, but the API refuses non-session mints: minting a deploy token is admin-equivalent and requires the web app (Settings → CI/CD Tokens). The command prints that guidance when refused. list and revoke work with any authenticated credential.

​
Run a deploy from CI

fjall ci run <deploy|destroy|build> <target> [service] is the single CI entry point — the same command both official plugins invoke. It forces non-interactive output, skips confirmation prompts, and rejects flags that don’t apply to the command you’re running. The full flag table, exit codes (including 2 plan-pending and 4 destruction-gate), and provider examples live in CI/CD Integration → Raw CLI Usage.

​
Next steps

CI/CD Integration

Full pipeline guide: plugins, tokens, AWS credentials, exit codes.

Engine Compatibility

How cli-version keeps the CI-installed CLI aligned with your constructs.