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
Since in terraform it's impossible to set the prevent_destroy lifecycle hook using variables (see hashicorp/terraform#22544) it would be nice if this could be handled by the provider.
My use case is that in dev environments, I want this provider to create/destroy databases without any issues and blockers. However, if I create/import a production database, it would be nice to mitigate potential danger of outright destroying a database. Since the type of environment is set via variables, setting the prevent_destroy lifecycle hook in code would cause problems in dev.
One implementation that would work is a remove_from_state_instead_of_delete bool input or something, which would do as it says: remove the database from state, but do not actually drop the database.
One workaround currently is to use a user without the grant to drop databases to manage resources in prod.
The text was updated successfully, but these errors were encountered:
This is a feature request.
Since in terraform it's impossible to set the prevent_destroy lifecycle hook using variables (see hashicorp/terraform#22544) it would be nice if this could be handled by the provider.
My use case is that in dev environments, I want this provider to create/destroy databases without any issues and blockers. However, if I create/import a production database, it would be nice to mitigate potential danger of outright destroying a database. Since the type of environment is set via variables, setting the prevent_destroy lifecycle hook in code would cause problems in dev.
One implementation that would work is a
remove_from_state_instead_of_delete
bool input or something, which would do as it says: remove the database from state, but do not actually drop the database.One workaround currently is to use a user without the grant to drop databases to manage resources in prod.
The text was updated successfully, but these errors were encountered: