-
Notifications
You must be signed in to change notification settings - Fork 4.3k
feat(bedrock-agentcore-alpha): make physical name properties optional for AgentCore resources #36354
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
base: main
Are you sure you want to change the base?
Conversation
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 fails with the following errors:
❌ Features must contain a change to an integration test file and the resulting snapshot.
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.
✅ A exemption request has been requested. Please wait for a maintainer's review.
|
||||||||||||||
|
||||||||||||||
|
Exemption Request: This change only makes physical name properties optional with auto-generation fallback - no new functionality or CloudFormation template changes that would require integration test snapshots. |
badmintoncryer
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.
Thank you for your contribution! I've added a minor comment.
| expect(memory.kmsKey?.keyArn).toBeDefined(); | ||
| }); | ||
| }); | ||
| // Tests for optional physical names (issue #36341) |
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.
I think this comment is not essential.
| // Tests for optional physical names (issue #36341) |
Could you please remove this line from gateway/runtime/browser.test.ts?
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 comment was included in all AgentCore resource tests...🤦
Thank you. I've deleted it.
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.
I've not realized that.. Sorry if you're asked by the maintainer to restore the comments.
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.
Your point is correct :)
These are all unnecessary comments that I added in this PR, so I should have deleted them.
badmintoncryer
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.
Thanks!
Issue # (if applicable)
Closes #36341.
Reason for this change
Improve AWS Bedrock AgentCore constructs by making physical name properties optional, following CDK best practices where names are auto-generated when not specified for better usability and to avoid naming conflicts.
Description of changes
Made physical name properties optional for all AWS Bedrock AgentCore constructs:
Names.uniqueResourceName()when names are omittedDescribe any new or updated permissions being added
None.
Description of how you validated changes
Added unit tests for auto-generation functionality for all constructs
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license