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
Thank you for opening an issue. Please provide the following information:
Terraform Version
Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
0.14
Affected Resource(s)
Please list the resources as a list, for example:
postgresql_grant
postgresql_default_privileges
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
# Copy-paste your Terraform configurations here - for large Terraform configs,# please use a service like Dropbox and share a link to the ZIP file. For# security, you can also encrypt the files using our GPG public key.
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.
Expected Behavior
What should have happened?
If schema not found, it should be recreated before checking/applying permissions
Actual Behavior
What actually happened?
provider searches for the non-existent schema and errors when it can't find it, also errors when it can't check the permissions on that schema
Error: could not find schema 'example-svc' while looking for owner
on ../../modules/rds-database-users-db-per-service/main.tf line 83, in resource "postgresql_grant" "service-crud":
83: resource "postgresql_grant" "service-crud" {
Error: could not revoke default privileges: pq: schema "example-svc" does not exist
on ../../modules/rds-database-users-db-per-service/main.tf line 94, in resource "postgresql_default_privileges" "service-schema-default-crud":
94: resource "postgresql_default_privileges" "service-schema-default-crud" {
Error: could not revoke default privileges: pq: schema "example-svc" does not exist
on ../../modules/rds-database-users-db-per-service/main.tf line 117, in resource "postgresql_default_privileges" "service-schema-default-sequence-crud":
117: resource "postgresql_default_privileges" "service-schema-default-sequence-crud" {
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
schema gets deleted externally for whatever reason
run terraform plan or terraform apply
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
GH-1234
The text was updated successfully, but these errors were encountered:
Hi there,
Thank you for opening an issue. Please provide the following information:
Terraform Version
Run
terraform -v
to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.0.14
Affected Resource(s)
Please list the resources as a list, for example:
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
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.
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the
crash.log
.Expected Behavior
What should have happened?
If schema not found, it should be recreated before checking/applying permissions
Actual Behavior
What actually happened?
provider searches for the non-existent schema and errors when it can't find it, also errors when it can't check the permissions on that schema
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
orterraform apply
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
The text was updated successfully, but these errors were encountered: