Closed shreddedbacon closed 1 year ago
with #150 we can handle this better
It should be able to be overridden by labels on the namespace so that in the event of migrations when the old namespace is cleaned up, it doesn't remove the repositories, or the robot account.
something like this perhaps?
harbor.lagoon.sh/cleanup-repositories: false
harbor.lagoon.sh/cleanup-robotaccount: false
When removing an environment with a regional Harbor, make sure to clean up the robot account if possible.