Import new heroku postgres addon #187
Merged
Conversation
This file contains 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
mvandenburgh
force-pushed
the
reimport-heroku-postgres
branch
from
a5af8cd
to
1f4884c
Compare
We recently upgraded our Heroku Postgres DB. This involved provisioning a new DB instance, which put our Terraform state out of sync.
mvandenburgh
force-pushed
the
reimport-heroku-postgres
branch
from
1f4884c
to
de64322
Compare
jjnesbitt
approved these changes
Sep 9, 2024
Merged
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.
We recently upgraded our Heroku Postgres DB. This involved provisioning a new DB instance, which put our Terraform state out of sync.
This resolves the erroneous plan in #186 which wants to create a new Heroku Postgres addon.