cloudposse/terraform-aws-route53-cluster-zone 0.2.5 on GitHub

what

Add enabled flag

why

For the terraform-aws-kops-state-backend we need to be able to disable the zone creation for kops gossip clusters which do not rely on DNS zones
Address #9

test

Set var.enabled == "false"
terraform plan

var.name
  The Name of the application or solution  (e.g. `bastion` or `portal`)

  Enter a value: app

var.namespace
  Namespace (e.g. `eg` or `cp`)

  Enter a value: eg

var.stage
  Stage (e.g. `prod`, `dev`, `staging`)

  Enter a value: dev

provider.aws.region
  The region where AWS operations will take place. Examples
  are us-east-1, us-west-2, etc.

  Default: us-east-1
  Enter a value: us-east-1

Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.


------------------------------------------------------------------------

No changes. Infrastructure is up-to-date.