Manage Deployments#

After a resource is deployed through Reply CMP, you can track its lifecycle, modify its configuration, detect drift from the desired state, view apply history, and safely decommission it — all without leaving the platform.

Navigate: left navigation → Provisioning → select an existing deployment from the list.

Deployment list#

The deployments list shows:

  • Deployment name

  • Template used (catalog item name)

  • Connection alias + provider

  • Status badge

Deployment status lifecycle#

Status

Meaning

Draft

The deployment has unsaved configuration changes; the live resource is unchanged

Valid

The last apply succeeded; the live resource matches the desired configuration

Tainted

An apply partially succeeded, or the resource is marked for deletion

Marked for deletion

A delete was requested; the Terraform destroy is in progress

Editing a deployment#

  1. Open the deployment → click Edit

  2. The configuration form (Step 3 of the wizard) re-opens with current values

  3. Make changes — inline validation applies

  4. Click Save → deployment moves to Draft status

  5. Click Review & Apply → a new dry run is offered; proceed to apply

Note

While a deployment is in Draft status, the live cloud resource is not changed. The change is applied only when you complete the Apply step.

Activity history and version restore#

The History tab on any deployment detail page shows:

  • A timeline of all apply operations

  • Timestamp, applied-by user, and a diff of what changed for each entry

  • A Restore button on each entry — click to load that version’s configuration back into the form

After restoring a version, a dry run is offered before applying.

Drift detection#

Reply CMP compares the Terraform state (what was last applied) against the live infrastructure state. Drift is detected when:

  • A resource property was changed outside of Reply CMP (e.g. a VM was resized in the Azure portal)

  • A resource was deleted outside of Reply CMP

When drift is detected, the deployment card shows a Drift Detected badge. Clicking it shows the diff between the desired state and the current live state.

Resolution options:

  • Re-apply — overwrite the live resource with the Reply CMP desired state (click Apply)

  • Sync — update the Reply CMP state to match the current live resource (imports the current live state)

Downloading the Terraform state#

For advanced debugging, the raw tfstate file is downloadable:

Advanced tab on the deployment detail page → Download state file → saves terraform.tfstate locally.

Warning

The tfstate file may contain sensitive values (credentials, connection strings). Handle it with appropriate security controls and do not commit it to source control.

Deleting a deployment#

  1. Open the deployment → click Delete

  2. Confirm the dialog — the deployment enters Marked for deletion status

  3. Reply CMP runs terraform destroy in the background

  4. On completion, status becomes Tainted and the resource card is greyed out

Post-delete: cost data for the deleted resource remains visible in FinOps history and Analyze views for audit purposes.