-
Notifications
You must be signed in to change notification settings - Fork 93
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
[BUG] "count" cannot be determined until apply #102
Comments
I ran into a similar issue today. What helped was actually removing the complete
|
I still have the same issue in both cases |
@grem11n, have you got a solution ? |
Same problem here. |
The full code example is down below.
|
Please, refer to the example of the module with To avoid this error, one has to also provide route table ids. |
For future searches, here is the updated vpc-peering module:
Now |
Thank you for your feedback ! |
Describe the bug
I just want to configure a VPC peering between 3 AWS account, but I have an error message "The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created."
The issue looks related to this : #83 but as you can see in my configuration, I have set
depends_on
.Terraform version:
1.4.6
Module version:
5.1.0
Error message:
Terraform code that produces the error:
Additional context
I use the "terraform-aws-modules/vpc/aws" module to create a VPC for each AWS account and I want to configure peering between theses VPC in the same terraform project.
The text was updated successfully, but these errors were encountered: