Fjall Docs — deploy AWS infrastructure into your own account

Read-only command. fjall list parses an application’s infrastructure.ts and prints the resources declared in it. It never calls AWS and never changes a file.

Overview

fjall list reads one application’s infrastructure.ts and prints every resource the codemod engine can locate: databases, storage, compute, and the rest. Use it to confirm what fjall add, fjall modify or fjall remove left behind before you deploy. The command is scoped to a single application, so -a, --app is required. For a fleet view, use fjall apps (lists applications) or fjall status (deployment health). fjall list reports declarations, not deployed state. A resource can appear here and not yet exist in AWS.

Prerequisites

Requirement	Why
An application exists	Run `fjall create application` (alias `app`) first, so an `infrastructure.ts` file exists
Run from the project root	The file is resolved as `fjall/<app>/infrastructure.ts` relative to your working directory

No Fjall login and no AWS connection are needed. The command reads local files only.

Usage

fjall list [type] --app <name>
# or use the alias
fjall ls [type] --app <name>

Arguments

Argument	Description	Required
`type`	Filter the output to one resource type	No

An unrecognised type exits with a validation error before the file is parsed.

Options

Option	Description	Required
`-a, --app <name>`	Application that owns the `infrastructure.ts` file	Yes
`--json`	Emit the resource entries as JSON to stdout and skip the table	No
`-v, --verbose`	Show detailed output	No
`--non-interactive`	Force plain CLI output	No
`--agent`	Enable agent output mode	No
`--budget <level>`	Output budget: `minimal`, `compact`, or a token count	No
`--fields <fields>`	Select exactly these output fields	No
`--full`	Disable content truncation	No

Resource types for `type`

Each type corresponds to one factory call in infrastructure.ts, so you can grep the file for the identifier in the right-hand column.

Value	Declaration it locates
`database`	`DatabaseFactory`
`storage`	`StorageFactory`
`compute`	`ComputeFactory`
`messaging`	`MessagingFactory`
`cdn`	`CdnFactory`
`network`	`NetworkFactory`
`pattern`	`PatternFactory`
`vpc-peer`	`VpcPeerFactory`
`vpc-peer-accepter`	`VpcPeerAccepterFactory`
`cross-plan-connection`	`CrossPlanConnectionFactory`
`organisation`	`OrganisationFactory`
`buildkite`	`BuildkiteFactory`

Examples

List every resource

fjall list --app api

Output:

Resources in api: 3

  File: /Users/you/acme/fjall/api/infrastructure.ts

  Name                  Type        File
  AppDatabase           database    /Users/you/acme/fjall/api/infrastructure.ts
  AssetBucket           storage     /Users/you/acme/fjall/api/infrastructure.ts
  ApiService            compute     /Users/you/acme/fjall/api/infrastructure.ts

The heading shows the application name and the resource count. Each row lists the resource name, its type, and the absolute path of the file it lives in. --non-interactive prints the same rows without the File: line and the column header.

Filter by type

Pass a resource type to narrow the output. The heading records the filter:

fjall list database --app api

Output:

Resources in api (type=database): 1

  File: /Users/you/acme/fjall/api/infrastructure.ts

  Name                  Type        File
  AppDatabase           database    /Users/you/acme/fjall/api/infrastructure.ts

JSON output

For scripts and pipelines, emit the entries as JSON. --json bypasses the table and writes a single line to stdout:

fjall list --app api --json

[
  {
    "type": "database",
    "name": "AppDatabase",
    "filePath": "/Users/you/acme/fjall/api/infrastructure.ts",
    "start": 412,
    "length": 268
  }
]

start and length are the character offset and span of the declaration inside the file, which is how fjall modify and fjall remove locate it. Pipe it through jq to pull out one field:

fjall list --app api --json | jq -r '.[] | select(.type == "storage") | .name'

Empty application

A newly created application with no added resources prints a zero count:

fjall list --app web

Resources in web: 0

  File: /Users/you/acme/fjall/web/infrastructure.ts

  No managed resources found.

With a type filter, the message names the type instead: No storage resources found.

Legacy declarations

A resource written in the older method form, such as app.addBuildkite({ … }), is listed with an (unmanaged) suffix:

  LegacyPipeline (unmanaged)   buildkite   /Users/you/acme/fjall/api/infrastructure.ts

fjall list sees these entries, but fjall modify and fjall remove refuse them. Rewrite the declaration in factory form to bring it back under codemod management.

How it works

Resolves fjall/<app>/infrastructure.ts relative to your current directory and exits if the file is missing.
Parses the file with the codemod engine, an AST parser that makes no AWS calls.
Collects every factory declaration it can locate.
Applies the type filter when you pass one.
Prints a table, or a JSON array with --json.

Common workflows

Confirm an added resource

fjall add database --app api --name AppDatabase --type Aurora --databaseName appdb
fjall list --app api

Confirm a removed resource

fjall remove deletes a declaration from infrastructure.ts. List afterwards to verify the file no longer carries it:

fjall remove storage --app api --name OldBucket
fjall list storage --app api

Inspect before deploying

fjall list --app api
fjall validate --app api
fjall deploy api

Troubleshooting

”Application name is required. Use —app flag”

fjall list is scoped to one application. Pass the name:

fjall list --app api

“Application ‘api’ infrastructure file not found at …”

The path in the message is where Fjall looked. Two usual causes:

You are not in the project root. cd to the directory that holds fjall/.
The application name is misspelled. Run fjall apps to see the real names.

Resource missing from the list

Check the type filter is not hiding it. Run fjall list --app api with no type to see everything.
Check for an (unmanaged) suffix elsewhere in the output. Legacy method-form declarations are listed but not managed.
Confirm the resource reached the file. Re-run fjall add if it did not.

fjall list reflects only what is declared in infrastructure.ts. To check what is actually deployed to AWS, use fjall status.

Next Steps

fjall add

Add a resource to an application’s infrastructure.

fjall modify

Change the properties of a declared resource.

fjall remove

Delete a resource declaration from infrastructure.ts.

fjall deploy

Deploy an application’s infrastructure to AWS.

Core Commands

Infrastructure Codemods

Insights

Management Commands

Build & CI

Environments & Data

Diagnostics & Recovery

Authentication

Agent Mode

fjall list

Overview

Prerequisites

Usage

Arguments

Options

Resource types for `type`

Examples

List every resource

Filter by type

JSON output

Empty application

Legacy declarations

How it works

Common workflows

Confirm an added resource

Confirm a removed resource

Inspect before deploying

Troubleshooting

”Application name is required. Use —app flag”

“Application ‘api’ infrastructure file not found at …”

Resource missing from the list

Next Steps

fjall add

fjall modify

fjall remove

fjall deploy

​Overview

​Prerequisites

​Usage

​Arguments

​Options

​Resource types for type

​Examples

​List every resource

​Filter by type

​JSON output

​Empty application

​Legacy declarations

​How it works

​Common workflows

​Confirm an added resource

​Confirm a removed resource

​Inspect before deploying

​Troubleshooting

​”Application name is required. Use —app flag”

​“Application ‘api’ infrastructure file not found at …”

​Resource missing from the list

​Next Steps

fjall add

fjall modify

fjall remove

fjall deploy

Overview

Prerequisites

Usage

Arguments

Options

Resource types for `type`

Examples

List every resource

Filter by type

JSON output

Empty application

Legacy declarations

How it works

Common workflows

Confirm an added resource

Confirm a removed resource

Inspect before deploying

Troubleshooting

”Application name is required. Use —app flag”

“Application ‘api’ infrastructure file not found at …”

Resource missing from the list

Next Steps