You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the dry-run option is supposed to ease migration, but the default behaviour of clients is to raise an exception on errors, so that would still make it a huge step. We could instead make that step easier with more configurable errors. #4076 gives the ability to remove errors from logs. But we could also have the following modes:
put errors in the response's extensions field so it would not raise exceptions
log errors but do not return them with the response
The text was updated successfully, but these errors were encountered:
Fix#4116
This makes authorization errors reporting more flexible, by configuring
response errors in one of two ways:
- authorization errors in the errors fields
- authorization errors in the extensions fields
- not returning errors to the client
This will work nicely with the dry-run option, allowing a test of
authorization that will not trigger exceptions in the client (due to the
`errors` field), and so an easier integration path.
Co-authored-by: Gary Pennington <[email protected]>
follow up to #4076 and #4079
the dry-run option is supposed to ease migration, but the default behaviour of clients is to raise an exception on errors, so that would still make it a huge step. We could instead make that step easier with more configurable errors. #4076 gives the ability to remove errors from logs. But we could also have the following modes:
extensions
field so it would not raise exceptionsThe text was updated successfully, but these errors were encountered: