-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
module requires two phase apply due to value of count cannot be computed
#13
Comments
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 14, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 17, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 17, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 17, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 17, 2018
This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13
joshmyers
added a commit
to cloudposse/terraform-aws-lambda-elasticsearch-cleanup
that referenced
this issue
Dec 17, 2018
* Add first cut of the ES cleanup module * Add working example usage This creates all the base resources necessary to test the elasticsearch-cleanup module. Unfortunately this requires a two stage apply as the `aws_route53_zone` resource fails to compute ID when passed into other modules. See: cloudposse/terraform-aws-elasticsearch#13 * Deploy Lambda artifact from S3 bucket Pull the deployment artifact from S3 using the new terraform-external-module-artifact module. This approach has the benefit of not checking in zip files into git, but the downside of more preamble when wanting to test this module as per the example docs. You need to know that the function should already be in S3 at a pre determined path. We need to think of proper deployment and promotion of these artifacts through different S3 buckets e.g. artifacts.testing.cloudposse.org -> artifacts.prod.cloudposse.org
@joshmyers I know this is an old issue but the workaround described here would allow you to complete this in one pass: |
I'm still running into this issue even with Terraform 0.13 and Module |
Gowiem
added a commit
that referenced
this issue
Sep 16, 2020
Implicit opt-in through checking dns_zone_id was causing folks problems as count / enabled need to be calculated during the plan which caused using target. See #13 + https://sweetops.slack.com/archives/CB6GHNLG0/p1600294860394500
aknysh
added a commit
that referenced
this issue
Sep 17, 2020
* Adds *_hostname_enabled vars for explicit opt-in to hostnames Implicit opt-in through checking dns_zone_id was causing folks problems as count / enabled need to be calculated during the plan which caused using target. See #13 + https://sweetops.slack.com/archives/CB6GHNLG0/p1600294860394500 * Updates examples/complete to fix tests * Update to `context.tf`. Update example. Update Terratest to `go` modules Co-authored-by: aknysh <andriy.knysh@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
what
While trying to test a new module, which depends on this one, I added example usage:
which failed with the below error:
This happens because the ID cannot be computed until after creation.
The workaround for this was using a two stage apply and passing the
-target
option.The text was updated successfully, but these errors were encountered: