-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decomission old AWI-CIROH infrastructure #4483
Comments
Shit, I just remembered we were supposed to wait until Monday. I got blocked on the AWS stuff though which is why I switched tack. For future reference, GitHub recognises and renders Obsidian flavoured markdown. So the following:
renders as: Warning Wait until Monday 29th July |
This is blocked now also anyway
I tried adding the relevant variables in the appropriate places in our code, but unless these variables are already in terraform state, it has no effect. |
Ok, after allowing my brain to stew in other ridiculous problems, I think my mistake here was trying to do a |
I used the Asset Inventory to check which resources where left over: https://console.cloud.google.com/iam-admin/asset-inventory/resources A lot of what's left in here are default resources (I think, I'm looking at the LogBuckets there) and enabled APIs. I deleted two object storage buckets, three VM instances, and a BigQuery service account that weren't cleaned up by terraform. |
I followed these steps to rename the workspace https://discuss.hashicorp.com/t/how-to-change-the-name-of-a-workspace/24010/2 |
Thank you, @sgibson91! |
#4238 is complete. We wait until Monday, July 29 and see if there are any user reported issues. If not, we decomission the old infrastructure.
awi-ciroh
terraform workspace. May need a git checkout from before Remove AWI-CIROH original cluster from CI/CD #4444 was mergedawi-ciroh
GCP project, make sure it's completely empty and all resources (including ones that were manually created for the transfer) are deletedawi-ciroh-2
terraform workspace toawi-ciroh
The text was updated successfully, but these errors were encountered: