-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat: Add support for network_type
#431
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
Conversation
network_type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you!
## [5.1.0](v5.0.3...v5.1.0) (2022-09-11) ### Features * Add support for `network_type` ([#431](#431)) ([a277924](a277924))
This PR is included in version 5.1.0 🎉 |
QQ, does changing |
@chenrui333 I assume that if you are not changing the value itself (but rather importing existing value), it should not prompt you to recreate anything. I have not tried this myself. |
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. |
Description
Add support for the
network_type
argument.Motivation and Context
I've got RDS clusters in production that need to be deployed in dual-stack mode, and this module didn't support that configuration yet. Instead of maintaining a private fork, I will submit a patch.
Breaking Changes
The required AWS provider is bumped from 4.6 to 4.28. This version is where the network_type argument became available.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request