IQSS/8252: Correct error response to 403/forbidden in test#8253
Merged
kcondon merged 1 commit intoIQSS:developfrom Nov 22, 2021
Conversation
sekmiller
approved these changes
Nov 22, 2021
Contributor
sekmiller
left a comment
sekmiller
left a comment
There was a problem hiding this comment.
Does what it needs to do. Thanks.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
What this PR does / why we need it: #8174 included a fix to report a request to the api/access/datafile/{id}/listRequests endpoint with a bad apikey to return 403/Forbidden instead of 400/Bad Request. The related AccessIT test wasn't updated to match.
Which issue(s) this PR closes:
Closes #8252
Special notes for your reviewer:
Suggestions on how to test this: Just run the IT tests / the AccessIT tests in particular.
Does this PR introduce a user interface change? If mockups are available, please link/include them here: no
Is there a release notes update needed for this change?:
Additional documentation: