Skip to content
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

Catch whitespace csv.spec.provider.name values #272

Conversation

komish
Copy link
Contributor

@komish komish commented Nov 22, 2022

This PR addresses cases where bundle validate fails to catch a provider.name value of " " as an empty value.

This solution trims whitespace for the value before evaluating for emptiness to address this case.

Signed-off-by: Jose R. Gonzalez jose@flutes.dev

Signed-off-by: Jose R. Gonzalez <jose@flutes.dev>
@komish
Copy link
Contributor Author

komish commented Nov 22, 2022

This issue was discovered here -> redhat-openshift-ecosystem/community-operators-prod#1869

@tedhtchang
Copy link

@komish Curious how does this PR affect operator-sdk bundle validate command, or CI test suites(kiwi, lemo, orange), or the OLM operator?

@komish
Copy link
Contributor Author

komish commented Nov 23, 2022

@tedhtchang bundle validate policy intends to prevent an empty provider name, but a value containing space characters and no other characters is not being treated as an empty value.

I can’t speak to the rest of the cases.

@acornett21
Copy link
Contributor

@J0zi or @mvalarh Do any of the community operators CI tests validate the content of the bundle? Or do you all rely on operator-sdk bundle validate directly to do the validation of the CSV? I believe CI tests reply on operator-sdk but I am not 100% certain.

@J0zi
Copy link

J0zi commented Nov 25, 2022

@acornett21 we rely on operator-sdk validation functionalities.

Copy link
Contributor

@perdasilva perdasilva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@joelanford joelanford closed this Jan 10, 2024
@joelanford joelanford reopened this Jan 10, 2024
@joelanford
Copy link
Member

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 10, 2024
Copy link

openshift-ci bot commented Jan 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelanford, komish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 10, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit e6998ff into operator-framework:master Jan 10, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants