Read-only command.
fjall status queries the Fjall API and
CloudFormation and prints a health report. It never changes AWS and never
edits a file.Overview
fjall status answers one question: which of my applications are up?
The application argument is optional, and it decides the scope of the report:
Both paths resolve the application from the Fjall API. Neither reads
fjall-config.json, so you can run the command from any directory. An
application name that your organisation does not carry is an error, not an
empty table.
Prerequisites
Missing credentials fail before the query with
Authentication required. plus
the cure for your environment: fjall login at a terminal, FJALL_API_KEY on a
CI runner. An unreadable AWS connection does not fail the command. The health
probe degrades to unknown and the report still prints.
Usage
Arguments
What the output shows
Two columns and a count line.− No applications found in place
of the table, and the summary reports Count: 0.
Health values
How health is derived
Two signals, in order:1
In-flight deployment records
Fjall reads your organisation’s recent deployment records. An application
with a record in
queued, pending, running or cancelling reports
deploying, whatever CloudFormation says. A compute-only rollout never
moves the network stack, so this signal is what makes those deploys
visible.2
The network CloudFormation stack
Otherwise Fjall reads the status of the application’s network stack
(
api becomes ApiNetwork) and maps it to one of the five values above.Health reads one stack per application, the network stack. A compute,
database or CDN stack that failed after its network stack settled still
reports
healthy here. Use fjall services <app> when you
need per-service rollout truth.Options
fjall status registers no options of its own. The six flags below are the
shared block Fjall registers across its commands.
There is no
--target, no --region and no --json. The report always uses
the active target, and it is the same plain text with or without
--non-interactive, because the command has no interactive UI. -v adds no
extra detail to this command’s output.
Machine-readable output
--agent switches the report to TOON, the structured format every Fjall
command emits in agent mode. See Agent mode for the wider
contract.
--fields narrows the columns. Only name and health are selectable:
VALIDATION_ERROR and lists the
valid fields. The check runs before authentication and before the API query, so
a typo costs nothing.
Exit codes
Pick the right command
fjall history is unrelated to deployment history. It browses the
infrastructure.ts snapshots that fjall add, fjall modify and
fjall remove write locally.Troubleshooting
”Authentication required.”
No usable credentials. Runfjall login, or set FJALL_API_KEY
on a CI runner.
Every application reports unknown
The CloudFormation probe could not read any stack. Usual causes:
- The AWS session has expired. Run
fjall connect. - No target is active, or the active target points at the wrong account. Check
with
fjall target getand set it withfjall target set <name>. - AWS is throttling the CloudFormation calls. Rerun after a pause.
Failed to query status: Application "web" not found
The name is not registered to your organisation. Run fjall status with no
argument to see the names Fjall holds.
An application reports healthy but the site is down
Health reads the network stack only. Run
fjall services <app> for per-service rollout state, and
fjall drift to find resources changed outside CloudFormation.
Next Steps
fjall services
Gate CI on live ECS rollout state and a non-zero exit code.
fjall releases
List recorded releases and roll back to a known-good one.
fjall deployments
Inspect, cancel and force-release your organisation’s deployments.
fjall deploy
Ship an application after the report shows it is out of date.