-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Failure when plan changes during apply-all #1419
Comments
This is actually a terraform bug (and specifically, an issue with the provider, as indicated in the error message). I would recommend reporting this on https://github.com/hashicorp/terraform-provider-aws. Side note: this looks awfully like hashicorp/terraform-provider-aws#14085 |
Thanks man we have the exact same problem ! Duplicate of hashicorp/terraform-provider-aws#14085 |
@yorinasub17 problem solved in https://github.com/terraform-aws-modules/terraform-aws-eks/releases/tag/v13.2.0 ! No more issue with tags, |
Glad to hear it was resolved! Thanks for closing the loop here! |
Hi there,
We currently use terragrunt to deploy all the stack of our infrastructure on AWS.
Starting from nothing, and building Networks, Security, EKS cluster, Data etc.
Context:
The issue we are facing is during the EKS step, as the plan changes during the apply-all, Terragrunt fails and needs a second execution of the apply-all to finish.
With more details, the error of the provider is :
The thing is, during the apply, EKS adds a tag which is :
Of course that tag was not present in the very first plan before the apply, as the value is computed at creation of the EKS cluster.
That causes the failure of the apply.
Is there any thing to do with terragrunt to "update" the plan during apply and successfully deploy in one time ?
Or is it only related to the aws eks provider ?
Thanks for your help !
Sylvain.
The text was updated successfully, but these errors were encountered: