Repository navigation
Adopt the 20 GiB RDS instance and stop managing the old one - #269
Merged
Merged
Conversation
Contributor
|
Terraform plan in terraform Plan: 0 to add, 0 to change, 0 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
Terraform will perform the following actions:
# aws_db_instance.default will no longer be managed by Terraform, but will not be destroyed
# (destroy = false is set in the configuration)
. resource "aws_db_instance" "default" {
id = "db-WEFHC5MZIA5NX5PBTQZPC2STZQ"
tags = {
"Name" = "incubator-prod-database"
}
# (74 unchanged attributes hidden)
}
Plan: 0 to add, 0 to change, 0 to destroy.
Warning: Some objects will no longer be managed by Terraform
If you apply this plan, Terraform will discard its tracking information for
the following objects, but it will not delete them:
- aws_db_instance.default
After applying this plan, Terraform will no longer manage these objects. You
will need to import them into Terraform to manage them again.✅ Plan applied in Terraform apply (OIDC) #109 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings Terraform in line after the #267 migration window. The two instances swapped identifiers by CLI: the 20 GiB instance is now
incubator-prod-databaseand the old 100 GiB one isincubator-prod-database-old.aws_db_instance.default(the old instance) moves to aremovedblock withdestroy = false, so Terraform stops managing it without deleting it. It gets deleted by hand later, with a final snapshot.aws_db_instance.incubator_prodtakes the identifierincubator-prod-database, matching what is live.Expected plan:
aws_db_instance.defaultleaves state, 0 to add, 0 to change, 0 to destroy, and nopostgresql_*changes. Do not merge if the plan renames or replaces either instance.Merge this before anything else on
main. Until it lands, any apply would try to rename the live database back toincubator-prod-database-new.Part of #267.