You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VM Instances aren't generated, and would be a good target for a handwritten sweeping function. We create a lot of them, so they're often left behind after test runs. They keep an entire network & it's associated routes, as networks can't be deleted if they have users.
We can probably skip instances managed by an igm/rigm, if that's easy to find.
Also we should prefix them all with tf-test.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
May 23, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
VM Instances aren't generated, and would be a good target for a handwritten sweeping function. We create a lot of them, so they're often left behind after test runs. They keep an entire network & it's associated routes, as networks can't be deleted if they have users.
We can probably skip instances managed by an igm/rigm, if that's easy to find.
Also we should prefix them all with tf-test.
The text was updated successfully, but these errors were encountered: