fix: primary key response should contain all parts of custom claims #3361
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.
Description of changes
When auth template process graphql responses, it should return all fields in custom claims
CDK / CloudFormation Parameters Changed
Issue aws-amplify/amplify-backend#2973
Description of how you validated changes
run build:
yarn buildcopied output to the project
cp -r ../../amplify-category-api/packages/amplify-graphql-auth-transformer/lib/ node_modules/@aws-amplify/graphql-auth-transformer/lib/Deployed changes and observed grapqhl contains all parts of custom claims on get/list
Checklist
yarn testpassesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
This probably requires a more though testing, or a more specialize test to isolate the regression and validate the fix. I also see
ownerEntitiesLaststored in snapshot tests etc which I couldn't check or test.