feat: Add AuthorizationCallback shared authorization type support #528
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Developers have no way to share
.authorization
configuration between their different schema featuresIssue number, if available:
Changes
This change introduces an
a.AuthorizationCallback
type which enables developers to define an auth callback once and reuse it in many.authorization
calls.Example:
Different callback sites have different requirements (schema offers
allow.resource
, customOperations can't receiveallow.guest().to(...)
content. Themodel
andfield
callback surface comes the mostauthorization
features and works in the most customer locations (not compatable with custom operations or ai kit conversations). For all special cases the customer wants to define for code sharing, the type can be overriden using a type param.Proposed Docs change
aws-amplify/docs#8269
Validation
Tests added for both type compatibility exploration and export surface feature coverage. This behavior has been manually tested in an example app definition.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.