-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Bug]: aws provider plugin crashing when running on GitHub with Atlantis #31857
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
terraform-provider-aws/internal/service/inspector2/delegated_admin_account.go Lines 204 to 229 in 219ab6f
calling terraform-provider-aws/internal/errs/errs.go Lines 15 to 22 in 219ab6f
|
This functionality has been released in v5.26.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.4.5
AWS Provider Version
4.63.0, 4.67.0
Affected Resource(s)
Expected Behavior
We're using Atlantis to run Terraform
plan
andapply
cycles on GitHub PRs. While working out proper IAM permissions, I am running repeated cycles to catch any permissions errors, adding the needed permissions, then running the cycle again. I should be able to do this until I have all permissions in place, then successfully apply the last cycle.Actual Behavior
I can successfully run ~6-7 cycles before the
apply
starts erroring with a message that the plugin has crashed when attempting theapply
. Thenplan
crashes as well. As a workaround I ran Terraform from my local machine with admin AWS permissions and successfully applied the remaining resources in the plan. Then when creating a new PR in the same module with new resources, theplan
still errors with the plugin crashing.Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
providers.tf
main.tf
terraform.tfvars
Steps to Reproduce
We are using Atlantis to run Terraform
plan
andapply
cycles on PRs in GitHub.After setting up the above configuration locally (while not using
terraform apply
, create a PR and push to our repository where Atlantis automatically runsplan
. We can then runatlantis apply
to attempt to apply the plan, but the apply errors with IAM permissions errors.After 6-7 cycles of adding permissions to our Atlantis, then re-running
atlantis plan
, then attempting to runatlantis apply
, the output changes to a panic error, saying that theaws-provider
plugin is crashing or not responding.This does not resolve with:
atlantis plan
aws-provider
plugin versionterraform init
In the provided configuration files, I'm attempting to add the
aws_kms_alias
resource after having some of configuration successfully applied with Atlantis and some having to be applied running Terraform locally. When creating the new PR to only stand up the alias resource, the plugin is still showing crashing/not responding errors.Atlantis and the
aws-provider
plugin will however continue to work in other modules in the same repository, and in other repositories.Debug Output
No response
Panic Output
apply
error 1apply
error 2 - re-running the applyapply
error 3 - running the apply after leaving it for the weekendplan
error 1 - after updating theaws-provider
versionplan
error 2 - after unlocking and discarding the plan, then replanningplan
error 3plan
error 4 - after deleting lockfileplan
error 5 - after unlocking and discarding the plan againplan
error 6 - after re-generating the lockfile withterraform init
New PR with new resource and previous plan applied with running Terraform locally as a workaround
Important Factoids
We are only encountering this issue when running Terraform through Atlantis. We do not have this problem when running Terraform on local machines.
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: