-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(cognito): new cloudFrontEndpoint
method for user pool domain without custom resource
#31402
base: main
Are you sure you want to change the base?
Conversation
…hout custom resource
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.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
cloudFrontEndpoint
method for user pool domain without custom resourcecloudFrontEndpoint
method without custom resource for user pool domain
cloudFrontEndpoint
method without custom resource for user pool domaincloudFrontEndpoint
method for user pool domain without custom resource
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
} | ||
|
||
/** | ||
* The domain name of the CloudFront distribution associated with the user pool domain. | ||
*/ | ||
public get cloudFrontEndpoint(): string { |
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.
This method name is based on the description in CFn doc.
The Amazon CloudFront endpoint that you use as the target of the alias that you set up with your Domain Name Service (DNS) provider.
- [Code Verification](#code-verification) | ||
- [Link Verification](#link-verification) |
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.
This change was triggered by my formatter. But it is in keeping with markdown etiquette, so I have left it as it is. If it needs to be erased, please let me know.
|
||
/* | ||
* Stack verification steps: | ||
* * Verify that the CloudFrontDistribution stack output is of the format 'xxxxxxxxxxxxxx.cloudfront.net' | ||
*/ | ||
|
||
const app = new App(); | ||
const app = new App({ postCliContext: { [LOG_API_RESPONSE_DATA_PROPERTY_TRUE_DEFAULT]: false } }); |
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.
To match existing snapshots. The integ test in CodeBuild CI failed when using context
instead of postCliContext
, so I use postCliContext
here.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue # (if applicable)
Closes #31342.
Reason for this change
UserPoolDomain
creates a custom resource to get CloudFront endpoint. However, CFn exposes the attribute natively now (see the issue). No custom resource is better if it is not needed.Description of changes
I propose a new method
cloudFrontEndpoint
without a custom resource.Three ways were originally considered. This method was chosen as it was the most reasonable of all.
1. Create a new method
This is the method submitted in this PR.
2. Rewrite an existing method directly
This causes destructive changes. Custom resources are not directly used in the user's application. However, this change will result in resource deletion in the user's CDK stack. This causes confusion for users and should be avoided.
Also, the existing integ tests that use the method will fail because the changes are considered as destructive changes.
3. Rewrite an existing method with a feature flag
An alternative to way 2, but a feature flag was avoided in this case as it leads to complexity. The design guidelines also recommend a new method.
Additional information
I avoided the feature flag in this PR, but there are situations where there are constructs that use an existing method, but cannot provide a new method for the constructs because it is used by a method implemented in the interface.
https://github.com/go-to-k/aws-cdk/blob/fcbdc769e681f1f915cdc8cd7aa3a565d807884d/packages/aws-cdk-lib/aws-route53-targets/lib/userpool-domain.ts#L14
I will make changes to those cases using a feature flag in a separate PR.
#31403
Description of how you validated changes
Both unit and integ tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license