Skip to content
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

feat: add output engine_version to force provider order #152

Merged
merged 3 commits into from
Oct 13, 2020
Merged

feat: add output engine_version to force provider order #152

merged 3 commits into from
Oct 13, 2020

Conversation

jurgenweber
Copy link
Contributor

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.

README.md Outdated Show resolved Hide resolved
@antonbabenko antonbabenko changed the title add output engine_version to force provider order feat: add output engine_version to force provider order Oct 13, 2020
@antonbabenko antonbabenko merged commit 9620cb3 into terraform-aws-modules:master Oct 13, 2020
@antonbabenko
Copy link
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
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants