-
Notifications
You must be signed in to change notification settings - Fork 853
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
Change log entry for releasing updated core for SRA Identity & Auth #4571
Change log entry for releasing updated core for SRA Identity & Auth #4571
Conversation
a896a0f
to
a0e1e06
Compare
a0e1e06
to
4e1a428
Compare
"type": "feature", | ||
"category": "AWS SDK for Java v2", | ||
"contributor": "gosar", | ||
"description": "This release contains a major internal refactor of authentication. The refactor is part of moving the SDK to Smithy Reference Architecture.\n\nIt paves the way for new features to be released over the coming months, e.g., SDK plugins and custom auth schemes. These will be released to individual service SDKs in a phased rollout.\n\nAlso, with this release:\n* custom 3rd party credential providers can be created with fewer SDK dependencies.\n* new signers can be used with fewer SDK dependencies.\n\nSince this is a major refactor, this release bumps the minor version of the SDK to 2.21. So keep an eye out for behavioral changes." |
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.
Is there a link for the smithy reference architecture? Or should we just say "a standardized AWS SDK architecture"
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.
How about:
This release contains a major internal refactor of authentication. The refactor is part of moving the SDK to a standardized AWS SDK architecture.
It paves the way for new features to be released over the coming months: SDK plugins to provide a unified interface to add third-party functionality to the SDK and the ability to define additional ways of authenticating with services.
With this release, custom 3rd party credential providers can be created with fewer SDK dependencies (with the new
identity-spi
module), and AWS signers can be used with fewer SDK dependencies (with the newhttp-auth-aws
module).Because this is a major refactor that may result in backwards-compatible behavior changes, this release bumps the minor version of the SDK to 2.21."
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.
It's planned to be published in Q4. I thought better to atleast use that terminology, so that later when someone is looking, they'll find 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.
Updated with Matt's suggestion
750ed27
into
feature/master/sra-identity-auth
SonarCloud Quality Gate failed. 9 Bugs 84.9% Coverage Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
Motivation and Context
Add changelog entry for the SDK core release for SRA Identity & Auth. Will merge this to the feature/master/sra-identity-auth branch first, before merging feature/master/sra-identity-auth to master (as part of #4509)
Modifications
Ran
./scripts/new-change
Testing
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License