Fix mapping of denied access in docker hub #8215
Merged
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.
Motivation
We are currently seeing error messages in the community test pipeline in -ext which indicate an error when verifying the access denied error of a docker push.
While it is not clear why there are different error messages returned here, we still have to map this return to AccessDenied (as it effectively is).
Changes
requesting higher privileges than access token allows
to be mapped to a AccessDenied exception