-
Notifications
You must be signed in to change notification settings - Fork 96
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
Configured destroy entrypoint (and body) not being invoked #116
Comments
What happens if you run |
Will try that and reply but that's certainly not what I want to do. Commenting it out is just the test to show how the "destroy" can be called. The actual use case is to pass a release number in the Also, notice in the debug output, some "destroy" is indeed being triggered, but my configured entrypoint/body are not called. |
Yeah, I'm mostly trying to figure out why it wouldn't be invoked in your environment. |
I attempted the https://gist.github.com/crandall-chow-bl/b5a427c276f6c2c6be0d402304affe53#file-destroy-txt This is on macOS 12.2.1 in case that matters. |
Unfortunately it looks like this is a Terraform Core issue: hashicorp/terraform#13549 |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
TL;DR
The configured
destroy_cmd_entrypoint
anddestroy_cmd_body
are not being invoked, even though the logs show the destroy was triggered and resource was removed from the.tfstate
.Expected behavior
On "destroy" (such as when TF needs to do a replace) the configured
destroy_cmd_entrypoint
anddestroy_cmd_body
should be invoked, similar to what happens on create, where thecreate_cmd_entrypoint
andcreate_cmd_body
are clearly invoked.Observed behavior
Creates are doing as expected, calling the configured entrypoint, but destroys are not. The
.tfstate
data is indeed created and destroyed as expected, but the custom entrypoints are never getting invoked.Terraform Configuration
Terraform Version
Debug Output
https://gist.github.com/crandall-chow-bl/b5a427c276f6c2c6be0d402304affe53
Additional information
Steps to Reproduce
The text was updated successfully, but these errors were encountered: