-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
rds/option_group: Fix bad diffs with version and port #33511
Conversation
Community NoteVoting for Prioritization
For Submitters
|
This functionality has been released in v5.18.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Description
Previously, on reading options back from AWS,
version
andport
would be set even if they weren't configured. This PR changes that to check first ifversion
and/orport
is set in the configuration before setting the value from AWS.This approach can be misleading in this scenario: a)
version
is set and applied, b)version
is removed from the configuration. Diffs inversion
will not be checked. (The same would be true ofport
.) A practitioner may assume that removing the value will clear or remove the value from the AWS infrastructure. However, removing the value from configuration will instead just mean that Terraform will not detect diffs forversion
in the future.Relations
Closes #21367
References
Output from Acceptance Testing