scorecard new API #3125
Merged
scorecard new API #3125
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
openshift-ci-robot
added
the
do-not-merge/work-in-progress
jmccormick2001
approved these changes
May 28, 2020
openshift-ci-robot
removed
the
do-not-merge/work-in-progress
estroz
suggested changes
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
estroz
reviewed
May 29, 2020
joelanford
reviewed
Jun 1, 2020
estroz
reviewed
Jun 1, 2020
jmccormick2001
approved these changes
Jun 4, 2020
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.
Description: To support additional scorecard2 features, we need the scorecard APi to be updated, for this, we need a new set of API structs that serve 2 key purposes:
--create a structure around the information presented by the List function (labels, image)
--create an ability for a test entrypoint to produce n-number of test results (e.g. suite of tests)
for this, the groupname/version will need to be updated and new golang structs will need to be generated/added