feat: add output engine_version to force provider order - #152
Merged
Conversation
antonbabenko
changed the title
Member
|
v2.28.0 has been just released. |
tomasbackman
pushed a commit
to qapital/terraform-aws-rds-aurora
that referenced
this pull request
Nov 16, 2020
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Description
I have added the engine_version output
Motivation and Context
context; hashicorp/terraform-provider-postgresql#2 (comment)
This is a helper to the postgres provider, to use its mechanics so there is a way you can instantiate your Aurora postgres instance and use the postgres provider in one run/plan.
Breaking Changes
No Breaking changes.
How Has This Been Tested?
I have tested it in my code base, plans now succeed even though the RDS has not been created yet.