-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
aws_elastic_beanstalk_environment Error: Provider produced inconsistent final plan #13823
Comments
Just got a similar issue
Everything was working fine so far, but I changed a value: |
@vanwalj if you are sure it is because of some change in rds cluster, then most probably there is something wrong with the config. I just saw that I was writing the wrong configuration for RDS here, and once I resolved my config for RDS, there were no more errors in other resources. Try it out, and let me know. |
@yashshanker just found what caused the issue, we were applying our terraform config in a ci pipeline using the docker |
I have a reproducible test case for this. First, create an SQS queue resource with a corresponding resource "aws_sqs_queue" "queue" {
name = "super_duper_queue"
max_message_size = 2048
visibility_timeout_seconds = 300
}
data "aws_sqs_queue" "queue" {
name = aws_sqs_queue.queue.name
depends_on = [aws_sqs_queue.queue]
} Then, pipe the report URL into an EB environment variable: // other directives cut for brevity
setting {
namespace = "aws:elasticbeanstalk:application:environment"
name = "SQS_QUEUE_URL"
value = data.aws_sqs_queue.queue.url
} It'll work on the first apply, but will stop working after that with the following error:
Commenting out the |
The same happens while changing cpu from 1024 to 256 in
Terraform v0.13.0
|
For folks running into the |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. 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. |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Panic Output
Expected Behavior
This is a part of a bigger configuration, which has all my infra's configuration. When I do
terraform apply
for the first time, it applies successfully and sets up my infra. Then subsequently, if I change anything, suppose security groups' ingress/egress CIDRs, it should apply and make those changes.Actual Behavior
The first
terraform apply
get applied successfully, but subsequently, when I do changes, suppose changes in security groups' ingress/egress CIDRs, it ends up with an error which is mentioned above.By the way, there are more settings in my elastic_beanstalk_environment resource, and this error is for all of them.
Steps to Reproduce
terraform apply
References
The text was updated successfully, but these errors were encountered: