-
Notifications
You must be signed in to change notification settings - Fork 89
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
EC stack update fails if there are configuration changes that are not in Terraform state #773
Comments
I have also ran into a similar issue:
Just trying to update to
My
Main difference is I don't think I actually changed anything in the console, and the failure doesn't show what the expected values should be (so that I can either change the console back, or add it to the terraform) |
I was able to resolve this by defining the missing autoscaling definitions in my terraform, but this wasn't previously necessary (they have never been there, and I've applied other changes) |
Can you clarify how you add the missing autoscaling changes? I tried adding empty block of other topology but that doesn't seems to help. Thanks
|
Readiness Checklist
Expected Behavior
Terraform Apply does the EC stack update independently of the changes on the stack configuration.
Current Behavior
When the Elastic Stack associated with the
ec_deployment
resource has an update pending and we run Terraform Apply, the provider fails to apply the update from time to time when theinstance_configuration_id
attribute changed on EC (due to autoscaling) and the provider tries to change its value at the same time as the EC stack version update. This will fail because currently, it is not possible to do cluster configuration changes at the same time as we do an EC stack version update.The error thrown is:
## Terraform definition
Steps to Reproduce
ec_deployment
resourceContext
This issue is affecting the provider's capability to update the EC stacks and it's blocking EC stack updates
Possible Solution
Your Environment
The text was updated successfully, but these errors were encountered: