Skip to content

Document need for care when deleting resources used by Git Runbooks#2628

Merged
steve-fenton-octopus merged 6 commits intomainfrom
cat/103829/deleting-envs-required-by-cac
Feb 18, 2025
Merged

Document need for care when deleting resources used by Git Runbooks#2628
steve-fenton-octopus merged 6 commits intomainfrom
cat/103829/deleting-envs-required-by-cac

Conversation

@caitlynstocker
Copy link
Copy Markdown
Contributor

@caitlynstocker caitlynstocker commented Feb 14, 2025

Background 🌵

When a user tries to delete an environment used by a DB Runbook, there are guardrails in place to prevent this. However with CaC Runbooks we can't maintain these guardrails as it's not practical to check every commit in a customer's repo to be sure there are no versions of their runbooks referencing a given environment.

There is a warning about this in the Unsupported Config as Code Scenarios page of the docs, but it's quite hidden away and we would like this info to be more readily available to CaC Runbooks users.

What's this?

This change just adds a couple of sentences to the CaC Runbooks doc warning against deleting required resources. And repeats a similar warning in the docs for channels, environments, lifecycles, tenant tags, worker pools and step templates.

What's it look like?

image

Fixes[sc-103829]
Fixes[sc-103789]

@caitlynstocker caitlynstocker requested a review from a team February 14, 2025 07:08
Comment thread src/pages/docs/runbooks/config-as-code-runbooks.md Outdated
@steve-fenton-octopus steve-fenton-octopus merged commit f62bfa0 into main Feb 18, 2025
@steve-fenton-octopus steve-fenton-octopus deleted the cat/103829/deleting-envs-required-by-cac branch February 18, 2025 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants