-
-
Notifications
You must be signed in to change notification settings - Fork 362
feat: Added a possibility to allow private hosted zone usage #250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
LGTM, please fix the docs by running |
bryantbiggs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, thanks @jgerry
|
@bryantbiggs Now we have some more extra work with AWS provider version 4. For now, I just locked it to version 3. |
|
Ya I just saw that dropped, I'll start taking a look later today 😅 |
## [3.11.0](v3.10.0...v3.11.0) (2022-02-10) ### Features * Added a possibility to allow private hosted zone usage ([#250](#250)) ([5a53f39](5a53f39))
|
This PR is included in version 3.11.0 🎉 |
## [3.11.0](terraform-aws-modules/terraform-aws-atlantis@v3.10.0...v3.11.0) (2022-02-10) ### Features * Added a possibility to allow private hosted zone usage ([terraform-aws-modules#250](terraform-aws-modules#250)) ([5a53f39](terraform-aws-modules@5a53f39))
## [3.11.0](terraform-aws-modules/terraform-aws-atlantis@v3.10.0...v3.11.0) (2022-02-10) ### Features * Added a possibility to allow private hosted zone usage ([terraform-aws-modules#250](terraform-aws-modules#250)) ([5a53f39](terraform-aws-modules@5a53f39))
## [3.11.0](terraform-aws-modules/terraform-aws-atlantis@v3.10.0...v3.11.0) (2022-02-10) ### Features * Added a possibility to allow private hosted zone usage ([terraform-aws-modules#250](terraform-aws-modules#250)) ([5a53f39](terraform-aws-modules@5a53f39))
|
Sorry if this is not a good place, but I think because of: terraform-aws-atlantis/main.tf Line 406 in 7803bcf
terraform-aws-atlantis/main.tf Line 137 in 7803bcf
route53_private_zone = true AWS is unable to validate ACM because the validation record is created on a private zone.
|
|
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Add a new boolean variable
route53_private_zoneto pass into the ALB moduleMotivation and Context
Add support for Route53 private hosted zones. Fixes #249.
Breaking Changes
no breaking changes
How Has This Been Tested?
examples/*projects.I have tested this by setting
route53_zone_nameto a public hosted zone, the module works as it did before my change. By settingroute53_zone_nameto a private hosted zone, and settingroute53_private_zonetotrue, I was able to create the appropriate Route53 entry in my private hosted zone.