Closed omada-jacob-smith closed 2 months ago
I see the same behavior with "auto_explain,pg_stat_statements"
.
Hey @omada-jacob-smith 👋 Thank you for taking the time to file this issue. Given that there's been a number of Terraform and AWS Provider releases since you initially filed this, can you confirm whether you're still experiencing the same behavior?
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. 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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform Version
$ terraform -v Terraform v0.12.20
Affected Resource(s)
aws_db_parameter_group (resource)
Terraform Configuration Files
Expected Behavior
I should be able to use both pg_stat_statements and pglogical
Actual Behavior
The parameter group seems to be stuck on pg_stat_statements and only pg_stat_statements
Steps to Reproduce
First, we were only using
"pglogical"
and that worked, then we updated the parameter to be"pglogical,pg_stat_statements"
. We ran a plan/apply and then onlypg_stat_statements
was in the parameter group. I tried setting it back topglogical
only and it still ispg_stat_statements
. The only way that I could get the values to work and for terraform to be content is to manually update the AWS UI. This has happened on four different databases/pg groups in exactly the same way.Important Factoids
Not that I know of.