You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @trombonax, my team has experienced the same issue. I believe it is more to do with the understanding of the schema attribute more than it needing to be in the state.
According to Postgres docs, the schema is only the location to install the extension's objects. There should only be one extension defined per db. I believe this is a problem in that you shouldn't be allowed to create a second extension in the same db with the same name (regardless of having a different schema). Please see my PR (#426) to address this by adding a check as part of the creation.
Hi there,
Thank you for opening an issue. Please provide the following information:
Terraform Version
$ terraform -v
Terraform v1.4.6
on linux_amd64
Affected Resource(s)
Terraform Configuration Files
Debug Output
[Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.](https://gist.github.com/trombonax/e9dd62c54b6936a77e80aece9c132429)
Panic Output
Expected Behavior
resource and state should not be changed
Actual Behavior
postgresql extension moving from schema to schema after each apply
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
many timesThe text was updated successfully, but these errors were encountered: