-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
release lock on SIGTERM too. #61
Comments
Additionally, terragrunt should forward SIGTERM signals to terraform. There is no guaantee that terraform will have received it. See also hashicorp/terraform#10459 |
In fact, on some cases (default on systemd services) SIGTERM is sent to all processes in the cgroup. In other cases (sysvservice, docker) the SIGTERM signal is only sent to the parent process. |
Good point. Looks like you have some code written for this already. Would you like to submit a PR? |
Yes, I will submit a PR once I get something with terraform. There are two aspects:
Are you ok with forwarding the SIGTERM signal ? When forwarding SIGTERM we must make sure terraform can handle it. Currently it does not respond to SIGTERM and doesn't cleanly finish like it does with Ctrl-C. I'm currently submitting a PR on terraform for that. |
Probably makes sense to wait for your PR to be merged into Terraform itself. |
yes |
This should have been fixed by #72. |
On SIGINT (Interrupt from keyboard), terragrunt release the lock, but not on SIGTERM (Termination signal). This should probably be fixed. See
locks/lock.go
.The text was updated successfully, but these errors were encountered: