-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Postgres provider: failure on destroy #5340
Labels
Comments
saliceti
changed the title
postgres provider: failure on destroy
Postgres provider: failure on destroy
Feb 26, 2016
This was referenced Feb 26, 2016
Configuring one provider with a dynamic attribute from another (was: depends_on for providers)
#2430
Closed
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Feb 29, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Feb 29, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Feb 29, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Feb 29, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Mar 1, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Mar 1, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
saliceti
added a commit
to alphagov/paas-cf
that referenced
this issue
Mar 1, 2016
The previous postgres job was doing some work to initialise the databases: create roles, create databases, enable extensions. Most of this work should have been done with the postgres terraform provider, but it has bugs and can't destroy the resources properly: hashicorp/terraform#5340 When this is fixed, we can move the create role and db tasks to terraform, but we still need to enable extensions.
Fixed by #10659 |
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. |
ghost
locked and limited conversation to collaborators
Apr 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like the dependency is not respected when destroying postgres roles, databases and RDS instance. However, the graph shows the dependency clearly.
This is with terraform 0.6.12.
Code:
Error:
The only way to solve this issue is to edit the state file manually...
The state file shows only the remaining postgres resources:
The text was updated successfully, but these errors were encountered: