[IAM-1155] - provide thrown error details in return from computePermissions #44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rsrebot
reviewed
Jan 10, 2024
reidblomquist
force-pushed
the
add/iam-1155-failure-reasons
branch
from
66ed7cf to
143f73f
Compare
rsrebot
reviewed
Jan 11, 2024
rsrebot
reviewed
Jan 11, 2024
reidblomquist
force-pushed
the
add/iam-1155-failure-reasons
branch
from
143f73f to
c0e8a43
Compare
reidblomquist
changed the title
reidblomquist
changed the title
rsrebot
approved these changes
Jan 12, 2024
…ssions so that clients ingesting might be better able to respond
reidblomquist
force-pushed
the
add/iam-1155-failure-reasons
branch
from
c0e8a43 to
ca52b1b
Compare
nicolapalavecino
approved these changes
Jan 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a backwards compatible change to support IAM platform work; specifically being able to provide denial reasons and/or remediation options when computing permissions.
Encapsulating this new information in a new
$errorsproperty on returned permissions keeps backwards-compatibility intact.See this epic for more info: https://mural.atlassian.net/browse/IAM-1149