Add API to create generic results #170
Merged
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
hluk
force-pushed
the
api-for-generic-results
branch
from
4b30677
to
defa816
Compare
The new /api/v3/results endpoint accepts the same data as POST /api/v2.0/results but supports OIDC authentication and permission control. Other users/groups won't be able to POST results to this endpoint unless they have a permission mapping with testcase pattern matching "ANY-DATA:<testcase_name>" (instead of just "<testcase_name>" as in the other v3 endpoints). JIRA: RHELWF-11168
hluk
force-pushed
the
api-for-generic-results
branch
from
defa816
to
a63768f
Compare
mvalik
reviewed
May 24, 2024
mvalik
approved these changes
May 27, 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.
The new /api/v3/results endpoint accepts the same data as POST
/api/v2.0/results but supports OIDC authentication and permission
control.
Other users/groups won't be able to POST results to this endpoint unless
they have a permission mapping with testcase pattern matching
"ANY-DATA:<testcase_name>" (instead of just "<testcase_name>" as in the
other v3 endpoints).
JIRA: RHELWF-11168