Infrastructure Configurations and Deployments

The Infrastructure area separates reusable configuration definitions from the recorded deployments created from them.

Configurations

Open Infrastructure > Configurations to search saved definitions or create a new one. A configuration contains the component model for all project environments.

From a configuration you can:

• edit components and environment settings;
• inspect the underlying configuration;
• analyse generated infrastructure output;
• deploy to the next environment;
• review metrics and prior deployments created from it.

Use Inspect Configuration for a read-only view or to copy the JSON when diagnosing a difference. Editing JSON directly should be reserved for changes you can validate against the visual component model.

Analysis

When analysis is available, review the generated template, lint or scan results, architecture diagram, and local test artifact before deployment. A clean analysis does not prove runtime correctness, but it can expose invalid templates, unexpected resources, or policy findings earlier.

Deployments

Open Infrastructure > Deployments to search recorded revisions. A revision is one deploy, destroy, or diff operation for an environment or shared resources.

The revision detail shows:

• configuration, environment, status, user, start time, and duration;
• the component/resource diff;
• per-cycle progress for shared and environment resources;
• overview and logs tabs;
• actions such as deploying the reviewed diff or abandoning an in-progress operation when available.

Diagnose a Failure

1. Open the failed revision and identify the failed cycle and component.
2. Read the first causal error in Logs, not only the final failure summary.
3. Compare the diff with the previously successful configuration.
4. Check AWS connection, region, permissions, quotas, names, and retained resources.
5. Correct the configuration and create a new deployment.

Do not repeatedly redeploy an unchanged failing configuration. A new attempt is useful only after the dependency, permission, quota, or configuration state has changed.