-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: modify olm-status-descriptor-test in scorecard #4009
Merged
varshaprasad96
merged 1 commit into
operator-framework:master
from
varshaprasad96:fix/scorecard-status-descrip
Oct 22, 2020
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# entries is a list of entries to include in | ||
# release notes and/or the migration guide | ||
entries: | ||
- description: > | ||
Modify `olm-status-descriptors-test` to only validate if the status-descriptors are present in CRD. | ||
# kind is one of: | ||
# - addition | ||
# - change | ||
# - deprecation | ||
# - removal | ||
# - bugfix | ||
kind: "bugfix" | ||
# Is this a breaking change? | ||
breaking: false |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought the whole point of this PR was to remove this check entirely @varshaprasad96?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since having
Status
field is suggested according the k8s-api conventions, have modified this check to add suggestions. Also this unit test ensures that ifObject
descriptor is nil, the scorecard test still passes.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of failing when
status
is not present in CR, suggestions are added. And we directly proceed with checking if thestatusDescriptor
is present in CRD or not. If the users input as described in #3999 is given with nostatus
field in CR, this test would pass.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A CR from
alm-examples
should never have a status according to #3999 (comment), so we shouldn't be suggesting that one be added. Whether the CRD defines astatus
field for a resource in its validation is another story.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm..okay. Because based on the comment, I tried creating a resource through console UI - with and without
status
field. And it worked in both the cases. And to verify if such CSVs exist withstatus
, just randomly went through the example community operators and found this.But considering we remove that validation check for that, can we remove the suggestion, or do you suggest we remove the entire
[StatusDescriptor]
(operator-sdk/internal/scorecard/tests/olm.go
Lines 232 to 284 in 9d27e22
Shouldn't we still check if
statusDescriptor
is present in CRD?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I shouldn't have said "never" above. The
alm-examples
can havestatus
blocks, but they should be treated as not existing. Therefore I'm only suggesting thecr.Object[statusDescriptor] == nil
condition be removed. Everything else is fine.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. Will create a follow up PR for this.