Fjall Docs — deploy AWS infrastructure into your own account

Prerequisites

A Fjall application created with fjall create app (or fjall apps create), so an infrastructure.ts file exists.
At least one declared resource to remove. Run fjall list -a <app> to see what the application currently declares.
Node 22.3 or later.

fjall remove edits source code. It does not delete deployed AWS resources. To tear down deployed infrastructure, use fjall destroy. To apply a removal to the cloud, run fjall deploy after editing.

Usage

fjall remove <type> --app <app> --name <Name>

Token	Meaning
`<type>`	Required. The resource category (see Resource types).
`-a, --app <app>`	Required. The application whose `infrastructure.ts` to edit.
`-n, --name <Name>`	Required. The resource name used when the resource was added.

A missing --app exits with Application name is required. Use --app flag. A missing <type> or --name exits with a validation error. Neither opens a prompt.

Resource types

<type> is one of these twelve exact values, the same set fjall add accepts: database, storage, compute, messaging, cdn, network, pattern, vpc-peer, vpc-peer-accepter, cross-plan-connection, organisation, buildkite. Anything else is refused before the file is read. fjall remove app is not a valid invocation and never touches AWS.

Resource names

Names must start with a letter and contain letters and digits only, up to 63 characters. PascalCase is the convention rather than a rule, so Analytics and analytics both validate. Use the exact name from fjall list -a <app>.

Examples

# Remove a database named ApiDb from the api application
fjall remove database --app api --name ApiDb

# Remove a storage bucket from the web application
fjall remove storage --app web --name WebAssets

# Remove a compute service, overriding the reference check
fjall remove compute --app api --name WorkerService --force

# Remove a queue with verbose logging
fjall remove messaging --app api --name EventsQueue --verbose

What happens

In an interactive terminal, Fjall confirms first and then runs the engine.

Confirm. A screen shows the target as <type> "<Name>", the absolute path of the file, and a warning that a backup is written before overwriting. The prompt defaults to No. There is no diff and no line-level preview.
Locate. The engine finds the managed XFactory.build("Name", …) call by shape.
Reference check. If the declaration binds a variable, the engine walks the file for live references to that binding. Remaining references block the removal unless --force is set.
Back up. The previous file is written to infrastructure.ts.bak and to a timestamped snapshot under the application’s .fjall/history directory.
Write. The declaration is spliced out and any import that became unused is pruned.

The success screen reports the lines added and removed, plus any references the engine found.

With --non-interactive, --agent, or any non-TTY stdout (every CI pipe), there is no confirmation screen. The removal is applied immediately.

The reference check

The check runs only when the resource is bound to a variable, such as const analytics = DatabaseFactory.build("Analytics", …). An inline declaration with no binding has nothing to reference, so it is removed without the check. When references remain, the command fails with exit code 11 and lists each one as <file>:<line>:<column> with its surrounding source. Delete or rewire those call sites, then re-run.

Force removal

--force removes the resource even when other declarations still reference it. The resulting infrastructure.ts can fail type-checking until you fix the dangling references. fjall remove does not run a post-write typecheck, so check the file yourself:

fjall remove compute --app api --name WorkerService --force
fjall validate --app api --deep

Exit codes

remove uses the codemod exit-code band, so a blocked removal is distinguishable from a crash in a script.

Code	Meaning
`0`	Resource removed.
`1`	Other failure.
`10`	Invalid invocation, unparseable file, or resource not found.
`11`	References remain. Re-run with `--force`, or rewire the call sites.
`12`	File I/O failure reading, backing up, or writing `infrastructure.ts`.

Recovery

Command	Restores
`fjall undo --app <app>`	The most recent `.bak` sidecar.
`fjall history --app <app>`	Lists the snapshots available to restore.
`fjall history --app <app> --restore <stamp>`	A specific snapshot, identified by its ISO 8601 timestamp.

Both commands require --app. See fjall undo and fjall history.

Agent and CI use

Agent mode applies the removal in one step. There is no dry-run stage anywhere in the codemod engine, so --agent always writes:

fjall remove database --app api --name ApiDb --agent

The structured result carries applied, type, name, path, linesChanged, and any references the engine found. On failure it carries the error and the exit code from the table above. --yes skips the interactive confirmation screen only. It has no effect with --agent or in a non-TTY shell, where nothing prompts in the first place.

Options

Option	Description	Default
`<type>`	Required. Resource type to remove (positional).	None
`-a, --app <name>`	Required. Application to remove the resource from.	None
`-n, --name <name>`	Required. Resource name.	None
`-f, --force`	Remove even if references to the resource remain in the source.	`false`
`--yes`	Skip the interactive confirmation screen.	`false`
`-v, --verbose`	Enable verbose logging.	`false`
`--non-interactive`	Force plain CLI output (no interactive UI).	`false`

Agent options

Option	Description
`--agent`	Enable agent output mode.
`--budget <level>`	Output budget: `minimal`, `compact`, or token count.
`--fields <fields>`	Select exactly these output fields.
`--full`	Disable content truncation.

Next Steps

fjall add

Add a resource to infrastructure.ts with the codemod engine.

fjall list

Inspect the resources an application declares.

fjall undo

Restore the most recent backup after a removal.

fjall validate

Typecheck the edited infrastructure.ts before deploying.

fjall deploy

Apply infrastructure.ts changes to AWS.

Add resources

Learn the resource-editing workflow end to end.

Core Commands

Infrastructure Codemods

Insights

Management Commands

Build & CI

Environments & Data

Diagnostics & Recovery

Authentication

Agent Mode

fjall remove

Usage

Resource types

Resource names

Examples

What happens

The reference check

Force removal

Exit codes

Recovery

Agent and CI use

Options

Agent options

Next Steps

fjall add

fjall list

fjall undo

fjall validate

fjall deploy

Add resources

​Usage

​Resource types

​Resource names

​Examples

​What happens

​The reference check

​Force removal

​Exit codes

​Recovery

​Agent and CI use

​Options

​Agent options

​Next Steps

fjall add

fjall list

fjall undo

fjall validate

fjall deploy

Add resources

Usage

Resource types

Resource names

Examples

What happens

The reference check

Force removal

Exit codes

Recovery

Agent and CI use

Options

Agent options

Next Steps