Error "value of 'count' cannot be computed" about terraform-aws-notify-slack HOT 7 CLOSED

It's something with Option 3 setup:

resource "aws_kms_key" "this" {
  description = "KMS key for notify-slack test"
}

resource "aws_kms_alias" "this" {
  name          = "alias/kms-test-key"
  target_key_id = "${aws_kms_key.this.id}"
}

// kms_key_arn = "${aws_kms_key.this.arn}"

becasue Option 1 works:

variable "kms_key_arn" {
  default = "arn:aws:kms:eu-west-1:835367859851:key/054b4846-95fe-4537-94f2-1dfd255238cf"
}

// kms_key_arn = "${var.kms_key_arn}"

from terraform-aws-notify-slack.

The problem is with this line:

data "aws_iam_policy_document" "lambda" {
  #count = "${var.kms_key_arn == "" ? 0 : 1}"
  count = 1 # or 0
  source_json = "${data.aws_iam_policy_document.lambda_basic.json}"

  statement {
..

Everything works

Related issue: hashicorp/terraform#17421

from terraform-aws-notify-slack.

@xliiv sorry for the delay in my response.

Yes, HCL2 will have it fixed. Meanwhile, you have to specify key using any of available options (static var, data-source, or pass from tfvars, or from CLI). Everything will work except computed values (${aws_kms_key.this.arn}).

There is not much this module can do about it to keep in an easy-maintainable condition.

from terraform-aws-notify-slack.

Does this mean that example doesn't work?
There is used ${aws_kms_key.this.arn}.

from terraform-aws-notify-slack.

You are right, it does not work as it is now in that example. My bad.

I will make a PR now which will fix this.

from terraform-aws-notify-slack.

v1.9.0 has been released. I've updated examples there.

Thanks a lot for opening this issue!

from terraform-aws-notify-slack.

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from terraform-aws-notify-slack.