Closed rafaelremondes closed 4 years ago
3.0.0 just came out, with some backwards incompatible changes, and we have not yet tested/upgraded this repo for it. As a short term workaround, you can pin your AWS provider to 2.x.x
.
Only one of the two parameters(
vpc_zone_identifier
,availability_zones
) should be passed right?
I think we want to pass both, but we probably need to change the default
for our corresponding input variables in consul-cluster
to be null
. Would you be up for a PR that makes that change?
Hey @brikis98
Yes, I pinned the provider-aws
version and it worked.
Sure, I'll test it and open a PR. Thanks for the help
:raised_hands: Thank you @rafaelremondes @brikis98 !
Fixed by @rafaelremondes in https://github.com/hashicorp/terraform-aws-consul/releases/tag/v0.7.7.
In the last version of the aws provider,
v3.0.0
, following conflicts appear for resourceresource/aws_autoscaling_group
when running aterraform plan
Related to this change: https://github.com/terraform-providers/terraform-provider-aws/pull/12927
Only one of the two parameters(
vpc_zone_identifier
,availability_zones
) should be passed right?