Skip to content

Conversation

MoonMoon1919
Copy link
Contributor

What it is

Why

If you don't require a DNS record to be created the previous default for the zone_id variable would still trigger a resource to be created, then cause the run to fail because the "false" zone_id doesn't exist.

@MoonMoon1919 MoonMoon1919 requested a review from osterman October 10, 2018 14:50
@osterman osterman requested a review from aknysh October 10, 2018 17:01
@osterman osterman merged commit d129bdf into master Oct 10, 2018
@osterman osterman deleted the bug/zone-id branch October 10, 2018 17:03
module "dns" {
source = "git::https://github.com/cloudposse/terraform-aws-route53-cluster-hostname.git?ref=tags/0.2.1"
enabled = "${var.enabled}"
enabled = "${var.enabled == "true" && var.zone_id != "false"}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think he did this because zone_id was previously set to false in a different PR.

https://github.com/cloudposse/terraform-aws-elasticache-redis/pull/13/files#diff-c9ac8098c5ea9d3e6a9a596ff0c512a4R107

Agree we should change this to our normal pattern.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's why I used this approach. Tonight I can remove the default value and submit a PR to address this. #26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants