-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
feat(cloudfront): Distribution - alternate domains #9699
Conversation
Enable users to associate one or more alternate domain names with a distribution. Originally, the plan was for this to come directly from the certificate (if provided); however, the `ICertificate` does not include the certificate domains. Given adding a certificate without specifying the aliases is effectively a no-op (the certificate will never be used), opted to make this an error instead of a warning (a breaking change). Open to discussion and debate on this point. BREAKING CHANGE: `domains` must be specified if `certificate` is provided.
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 great! One tiny cosmetic comment that you can incorporate if you want.
I set the label to pr/do-not-merge
, feel free to remove at your leisure 🙂.
Courtesy Adam Co-authored-by: Adam Ruka <adamruka@amazon.com>
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Enable users to associate one or more alternate domain names with a
distribution. Originally, the plan was for this to come directly from the
certificate (if provided); however, the
ICertificate
does not include thecertificate domains.
Given adding a certificate without specifying the aliases is effectively a
no-op (the certificate will never be used), opted to make this an error instead
of a warning (a breaking change). Open to discussion and debate on this point.
BREAKING CHANGE: Distribution:
.domains
must be specified ifcertificate
is provided.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license