Deploy from Catalog#

Provisioning in Reply CMP uses an internal catalog of Terraform-backed service templates. You fill in a guided form, the platform generates a plan and previews it with an AI summary, then you apply it. The deployment is tracked throughout its lifecycle.

Navigate: left navigation → Provisioning → New Deployment (or click “Deploy from Catalog”).

Step 1 — Choose a catalog item#

Browse available service templates. Each tile shows:

  • Provider badge (Azure / AWS / GCP)

  • Template name (e.g. “Azure Kubernetes Service”, “AWS S3 Bucket”)

  • Short description

  • Required fields preview

Use the search bar to filter by name. Use the provider filter to narrow by cloud. Select a template to proceed.

Note

The template catalog is managed by your platform team. If a resource type you need is not available, contact your administrator to request it.

Step 2 — Resource details#

Field

Description

Resource name

Max 40 characters; must be unique within the connection

Connection

The cloud account to deploy into. The alias (e.g. default, prod, dev) is shown in the dropdown

Region

Provider region (choices depend on the selected template)

Click Next to continue.

Step 3 — Configuration#

A dynamically generated form based on the selected template’s JSON Schema. The form validates inline as you type.

Feature

Description

Required fields

Marked with an orange asterisk; form cannot advance until complete

Completion progress bar

Shows % of required fields filled; reaches 100% before enabling Next

Inline validation

Errors appear per-field in real time — no need to submit to discover them

JSON toggle

Click “View as JSON” to switch to a raw JSON editor

Default values

Some fields are pre-filled; review before modifying

Tip

Use the JSON view toggle to paste a configuration from a previous deployment or an external source. The form and JSON view stay in sync.

Step 4 — Review and Deploy#

Dry Run (Plan)#

Click “Run Dry Run” to preview what will be created without making any changes:

  • A terminal-style output pane shows the Terraform plan

  • CREATE / MODIFY / DESTROY counts are displayed

  • An AI Plan Summary appears below the terminal: a plain-language description of what will be created

Review the summary and the plan output. If everything looks correct, click Create.

Apply#

The platform runs terraform apply. Progress is shown in the terminal pane. When complete:

  • Success: an AI Plan Summary (post-apply) describes what was created; a link to the new resource in Discovery is shown

  • Failure: an AI Error Explanation describes in plain language what went wrong and suggests corrective actions; the raw Terraform output remains available for investigation

Note

The AI Plan Summary and Error Explanation are generated by Azure OpenAI and may not be 100% accurate in edge cases. Always cross-check with the raw Terraform output if you are unsure.

Connection aliases#

When your tenant has multiple connections per provider, each one has an alias:

Alias

Typical meaning

default

The first connection added for the provider

prod

Production account

dev

Development / sandbox account

custom

Set by the administrator when creating the connection

Select the correct alias carefully — deployments go to the cloud account associated with the alias.