ci: run terraform apply
in provider example test with timeout
#3482
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
GitHub actions are run with a 6 hour internal timeout, after which running steps are terminated.
The termination signal is not properly forwarded to the running Terraform process, leading to resources not being cleaned up and state information potentially being lost.
For us, this only happens when there is an internal error during the
constellation apply
stage of the terraform provider, which is ran without any timeouts.Since
terraform apply
does not support any global timeout flags, we may hit the 6 hour mark during this step.Proposed change(s)
terraform apply
withtimeout
to stop execution of apply after 1 hour, or 4 hours for upgradesterraform destroy
Related issue