Environments

Deleting an environment

What goes, what survives, and why Kuppit sometimes refuses.

Deleting a named environment destroys its resources and their data, stops its hostnames answering, and removes it from the project. Before you confirm, Kuppit lists exactly that, resource by resource, and asks you to type the environment's name.

Preview environments are not deleted by hand: they go when their pull request closes. See preview environments. Production cannot be deleted on its own; delete the project instead.

What goes

From the environment's Overview, choose Delete environment. The dialog says what deleting means for this environment:

Each web service is destroyed, along with its deployment history.
Each database the environment owns is destroyed with all of its data.
Each hostname stops answering.
The environment disappears from the project. Usage history is kept for billing.

Deletion is durable rather than instant: Kuppit records the request, takes you back to the project, and tears the environment down in the background. Routing is withdrawn before anything is destroyed, so nobody holding a URL sees a half-removed service.

What survives

A resource this environment uses from another environment is not deleted. The dialog says so: it belongs to its owner, and this environment simply stops using it. The owner is untouched. Deleting an environment that shares Production's database never touches Production's data.

A database that was cloned from another environment is this environment's own, and is destroyed. The environment it was cloned from does not know or care; cloning records where the data came from and nothing more.

When Kuppit refuses

An environment whose database is shared by other environments cannot be deleted while they use it. Kuppit refuses with the list:

Other environments share this one's resources: staging, qa. Delete or detach them first.

Delete those environments first, or remove the shared database from each of them, and try again. Deleting the environments that share, in any order, always converges: each one stops using the database, and the owner can then go.

The same rule applies to a single shared database: the environment that owns it cannot remove it while another environment uses it.

Was this page helpful?

Named environments

Create a long-lived environment such as staging from an existing one, deciding per resource whether it gets its own copy, shares, clones or does without.