Skip to content
This repository was archived by the owner on Feb 5, 2020. It is now read-only.

Conversation

@kbrwn
Copy link
Contributor

@kbrwn kbrwn commented Mar 19, 2018

  • This originally found here.
  • This change has been tested on tectonic 1.8.9

@kbrwn kbrwn requested review from robszumski and zbwright March 19, 2018 20:50
robszumski
robszumski previously approved these changes Mar 19, 2018

* __module.dns.data.aws_route53_zone.tectonic: data.aws_route53_zone.tectonic: no matching Route53Zone found"__

Deploying to an private route53 dns zone using the `tectonic_aws_external_private_zone` parameter can result in failure to dectect the zone by the installer. This can be resolved by configuring terraform route53 module with the `private_zone` parameter.
Copy link
Contributor

Choose a reason for hiding this comment

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

... a private Amazon Route 53 DNS zone ... Terraform Route 53 module ...

* __module.dns.data.aws_route53_zone.tectonic: data.aws_route53_zone.tectonic: no matching Route53Zone found"__

Deploying to an private route53 dns zone using the `tectonic_aws_external_private_zone` parameter can result in failure to dectect the zone by the installer. This can be resolved by configuring terraform route53 module with the `private_zone` parameter.
Deploying to an private Amazon Route 53 DNS zone using the `tectonic_aws_external_private_zone` parameter can result in failure to dectect the zone by the installer. This can be resolved by configuring Terraform Route 53 module with the `private_zone` parameter.
Copy link
Contributor

Choose a reason for hiding this comment

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

Deploying to a private ...

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants