-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[New Data Source]: aws_rds_cluster_parameter_group and aws_db_parameter_group #33761
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
As of today |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
@johnsonaj @benjamin-wright the newly added data sources are not doing what was described in this issue and are not helpful. I'm not sure if there is even a point to their existence. they need to return the parameters and values to be useful. |
also referenced here #13718 (comment) if its helpful i can open a new issue to ask for that to be added |
This functionality has been released in v5.62.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
A data source for parameter groups would be helpful. One specific use case is related to this problem #22857 which cannot be solved via Terraform.
With a data source I could compare parameters that are being set to what the defaults are and avoid trying to set them if the value already matches avoiding the persistent diff occurring as a result of the issue linked above.
Requested Resource(s) and/or Data Source(s)
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: