Skip to content

0.14.0 Fix `count` for resources
Compare
Choose a tag to compare
@aknysh aknysh released this 04 May 18:32
0.14.0
389867d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

what

  • Fix count for resources
  • Don't use data sources in counts

why

  • When an output from a data source is used in counts, in some cases Terraform can't compute the counts throwing the errors (it's working in the Terratest, but does not work for some customers):
Error: Invalid count argument
 on .terraform/modules/search_service_elasticsearch_master.elasticsearch/main.tf line 76, in resource "aws_iam_service_linked_role" "default":
 76:   count            = var.enabled && var.create_iam_service_linked_role && length(data.aws_iam_role.default.*.id) == 0 ? 1 : 0
The "count" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the count depends on.
  • We have a bool variable create_iam_service_linked_role to control that without using data sources. If the AWS account (where the module is provisioned) already has the AWSServiceRoleForAmazonElasticsearchService service role, set the variable create_iam_service_linked_role to false. On a new account, set it to true
Assets 2
Loading