-
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_codedeploy_deployment_group issues with load_balancer_info #10836
Comments
Thanks for submitting this issue, @apenney. Could you add some more detail to the example? Specifically:
|
It does the same thing regardless of the instance_count; well, it tries to obviously change:
Other resources:
|
Hi @apenney, I'm finally getting back to this. I think I've located the error, and I will work on a fix for this. |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Terraform Version
❯ terraform -v
Terraform v0.12.13
Affected Resource(s)
Terraform Configuration Files
Here's a direct cut and paste from my resource. Originally I was using the dynamic hack as you can see below (commented out). In order to rule this out I added a direct load_balancer_info{} block to make sure it wasn't that.
Debug Output
Sorry, the full output has a bunch of stuff I can't paste, but I assume this is the heart of what's going on:
2019/11/11 09:37:05 [WARN] Provider "aws" produced an invalid plan for module.web.aws_codedeploy_deployment_group.app, but we are tolerating it because it is using the legacy plugin SDK.
The following problems may be the cause of any confusing errors from downstream operations:
- .deployment_style: block count in plan (1) disagrees with count in config (0)
I can provide the full output privately if needed.
Expected Behavior
When I run this I expect it to associate the target group with the codedeploy group but this step is always skipped, no matter how much I mess around and tweak the config. Originally (I think?) this worked, I am pretty sure I manually verified this when I originally wrote this terraform, but somewhere along the way it stopped working.
I can no longer associate target groups with codedeploy, no matter what I do. Adding it by hand does not inspire terraform to try and remove it either, it completely ignores this block.
Actual Behavior
Nothing, a terraform plan is blank.
Steps to Reproduce
I'm hoping you can simply create a target group and attempt to associate it with codedeploy in any way and see it fail.
terraform apply
Important Factoids
Nothing that I can think of, this is all new stuff.
The text was updated successfully, but these errors were encountered: