Overriding Resources
Override resource configuration per environment in Facets without changing the blueprint, using Form or JSON mode, version history, and rollback.
The Overrides tab changes a resource's configuration at the environment level, without touching the blueprint. Use it when an environment needs to deviate from the blueprint: an environment-specific value, a hotfix in a live environment, or a configuration you want to test in one place before rolling it wider.
What you can do
- Form or JSON mode: edit through a guided form, or edit the JSON directly for precise control.
- Blueprint vs. override comparison: in JSON mode, diff the blueprint against your override to see exactly what changed.
- Environment variables: view and edit the resource's environment-specific variables in context.
- Version history and rollback: compare override revisions, inspect a change, and roll back.
- Secrets and variables in context: see which secrets and variables the resource uses and what they resolve to while you edit, without leaving for the Secrets & variables page.
Performing an override
Using prompt
Set service/api to 10 replicas in prod only.or
Using command
raptor apply override service/api -p PROJECT -e ENVIRONMENT --set spec.replicas=10--set merges into the existing override, so fields you do not mention are left alone.
Values are type-inferred: true, false, numbers and JSON are parsed, anything else
stays a string. Use --set-json when you want invalid JSON to fail rather than silently
become a string, and --set-string for a field that holds serialized JSON as text.
--unset spec.some.field removes a field from the override. That releases the pin, so
later blueprint edits reach this environment again.
Add --dry-run to print the override without applying it.
New to the CLI? Install it first.
- Pick Form mode for a guided interface, or JSON mode for direct editing.
- Make your changes. In JSON mode, use the blueprint vs. override comparison to review the diff.
- Save to apply the new configuration to the resource in that environment.
Some module fields can only be set per environment, never in the blueprint. Where such a field is required and this environment has not set it, the Overrides tab shows a warning, so the gap is visible here rather than surfacing when a release fails.
Version history and rollback
Every override change is kept as a revision, so you can compare and revert.
Using prompt
Roll back the override history on service/api in prod.or
Using command
raptor get overrides service/api -p PROJECT -e ENVIRONMENT --history --diffraptor rollback override service/api -p PROJECT -e ENVIRONMENTThe first lists the revisions and diffs the latest against the previous one; --diff=v2..v5
compares any two. The second restores a revision, defaulting to the one before the current
change, with --version N to pick another from the history.
A rollback is recorded as a new revision whose content equals the target, so history is
never rewound and a rollback can itself be rolled back. The command prints the
effective-configuration diff and asks for confirmation before writing; --yes skips the
prompt. The environment picks up the restored configuration on its next release.
New to the CLI? Install it first.
- In the History section of the Overrides tab, review the chronological list of changes.
- Select two revisions to compare their configurations side by side.
- Open a revision to see its detailed changes.
- Roll back to a prior revision to revert the resource to that configuration.
Deleting an override
Delete one overridden field, or clear every override on a resource in an environment.
Using prompt
Remove the memory override on service/api in prod.or
Using command
raptor delete override service/api -p PROJECT -e ENVIRONMENT --path spec.runtime.size.memoryraptor delete override service/api -p PROJECT -e ENVIRONMENTWith --path, repeatable, only the named fields go. That is the same operation as
selecting overrides in the console. Without --path, every override on the resource goes
and it reverts to its blueprint definition in that environment. -e takes more than one
environment in either mode, so one call can clear a field across all of them.
The override document and its version history survive a delete either way.
New to the CLI? Install it first.
- Open the Overrides Summary tab in the resource side-pane.
- Select the overrides you want to delete.
Deleted fields revert to their blueprint default. Changes go live on the resource's next release.
Troubleshooting
| Problem | Solution |
|---|---|
| Override changes are not live | Confirm the change is saved with no validation errors, and that a release has run for the resource since. |
| Configuration conflicts | Use the blueprint vs. override comparison to find and resolve the discrepancy. |
| A rollback did not take effect | Check the version history for intermediate changes, and make sure a release ran after the rollback. |
Resource Live Insights & Operations
The Live tab in Facets gives real-time insights and operations for a deployed resource: pipeline activity, Kubernetes dashboard, Terraform outputs, and metrics.
Release History
Use the Release History tab in Facets to track a resource's blueprint, override, and artifact changes, view Terraform logs, and roll back to prior versions.