prevent_destroy should allow plan to succeed

### Terraform Version 0.10.7 ### Output ``` Error running plan: 1 error(s) occurred: * aws_db_instance.db: 1 error(s) occurred: * aws_db_instance.ics_db: aws_db_instance.db: the plan would destroy this resource, but it currently has lifecycle.prevent_destroy set to true. To avoid this error and continue with the plan, either disable lifecycle.prevent_destroy or adjust the scope of the plan using the -target flag. ``` ### Expected Behavior I would like to know *why* it wants to destroy it. This is provided when `prevent_destroy` is `false` by means of `(forces new resource)` ### Actual Behavior Plan is interrupted before any useful information is displayed. ### Steps to Reproduce 1. `terraform init` 2. `terraform plan` ### Important Factoids Current workaround is to turn `prevent_destroy` off (dangerous!!!) and to run `plan` again to see cause. In this case it is due to [this open issue](https://github.com/terraform-providers/terraform-provider-aws/issues/507)

Posted by beanaroo on Oct 18, 2017, 7:31 PM

Tags

• github (Software)

Related issues

• [Meta] Feedback on granular control over Copilot changes
• unexpected status 401 Unauthorized issue
• [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
• [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
• Video stops playing after some minutes
• [MODEL] Claude verbose code comments by default — ignores instructions to stop.