After a deploy

A deploy leaves ordinary platform resources behind. Nothing keeps them tied to the blueprint: you manage each of them where you manage any resource of its kind.

The container instance

The stack runs as a container instance with the instance name, listed under Container Instances. Its overview shows Template — the blueprint's slug and the version it was deployed from. Starting, stopping, logs, scaling and changes all happen there, as for any other container instance — see Container instances. The addresses the stack is reached at are the instance's endpoints — see Endpoints.

A deployed instance does not follow later versions of its blueprint. It keeps running as deployed when the blueprint is updated or removed from the catalog.

Managed resources

Each database the blueprint declared is a PostgreSQL resource named <instance>-<name> in the same resource group, managed like a database you created yourself. A blueprint that offers high availability and has it chosen gets three database instances; otherwise one.

The instance vault

The vault <instance>-secrets holds:

• every secret parameter — entered, generated or composed on deploy — under the parameter's name;
• each managed resource's connection details, under the keys the blueprint names.

The parameters the blueprint generates or composes are marked Template-managed in the vault — also when you typed the value yourself — see Secrets created by a template. Connection details of managed resources are not marked. The instance's identity has Secrets Reader on the vault, and each component receives the values when its containers start: after you change a value, a component picks it up at its next restart.

Addresses and credentials

A blueprint can declare outputs — the URL of an admin console, a username — but the portal does not show them anywhere today. Find the addresses on the container instance's endpoints and the credentials in the instance vault.

Delete the instance

Deleting the container instance:

• removes its containers;
• deletes its vault <instance>-secrets and every secret in it, for good. The confirmation dialog says so;
• leaves the managed resources where they are. Delete a database yourself when you no longer need it: deploying again under the same instance name picks up the database that was left, with its data, rather than creating a new one.

Because the vault goes too, the delete needs secretvault/delete on the vault as well as containerinstance/delete. Without it, the platform refuses the delete before anything is removed, and the confirmation dialog offers Request temporary access for Contributor on the vault; once an owner approves it and you activate it, delete again.

When the blueprint goes away

Deleting a boundary template, removing a catalog source, or a blueprint disappearing from the platform catalog leaves every instance deployed from it running. Its Template still names the slug and version it came from.