Archive an Environment

Archive an environment to make it read-only while keeping its setup and history.

Goal

Pause an old release flow without deleting its configuration.

Prerequisites

• Permission to archive environments
• The target environment to archive

What you need

• The environment you want to archive
• Confirmation that active changes should stop in this environment

Using Devopness MCP

Try these prompts in Devopness MCP:

• "Archive the legacy-staging environment in acme-platform"
• "Archive the old hotfix environment in my project"

After you save

• The environment becomes read-only
• Settings, history, and team memberships stay in place

Verify

• The environment appears in the archived list
• You cannot make active changes in it

Common issues

• You cannot archive: check for resources that still need manual cleanup
• You do not have permission to archive this environment

What to do next

• Find an archived environment
• Unarchive an environment when you need it active again