Allow skipping the active instances check when deleting a service
rejected
A
Agreed Mockingbird
Hey team, do you think it’s feasible from you side to add a new setting at the account/org/project level, which will be called something like “Don’t check for active instances when deleting”? This new check in nextgen creates a lot of confusion and doesn’t have any value for us, because we never had a problem with this in firstgen, where it didn’t exist.
Log In
A
Agreed Mockingbird
Currently it's possible to remove such services using the "force delete" option, and your support actively promotes it in case when services need to be deleted. The problem with this setting is that it can potentially create more issues with broken links between different instances, like when an env is used in a pipeline or something similar, so sometimes we have to enable this setting, remove a service, and then disable it again.
We've also seen cases when a service cannot be removed even after all instances were cleaned up and we had to wait for a few hours.
This check causes our terraform runs to fail and alerts to fire, and in many cases it was a false positive.
Rohan Gupta
rejected
Unfortunately no, our licensing framework enforces that we let users know when they are deleting instances because they are billed on active service instances.