-
Notifications
You must be signed in to change notification settings - Fork 53
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
Correctly validate crd.spec.versions #189
Conversation
Hi @tiraboschi. Thanks for your PR. I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
@tiraboschi: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
New changes are detected. LGTM label has been removed. |
/retest |
Hello, ERROR: CSV.spec.crd.owned.version isnot in CRD.spec.versions list [manifests/myapp-operator.clusterserviceversion.yaml] operator-courier --version2.1.8 |
/retest |
/hold |
crd.spec.version got deprecated for crd.spec.versions but in this case we are going to access a list of dictionaries where the relevant value is in the name field. Fix all the validations on spec.versions and add additional validations. Fix also its test. Signed-off-by: Simone Tiraboschi [email protected] Fixes: operator-framework#188
/unhold |
I updated https://github.com/tiraboschi/operator-courier/tree/fix_188 but strangely I still my latest changes here |
Github is having problems - I saw similar odd behavior in unrelated PRs - just have to wait for them to fix the infrastructure: https://www.githubstatus.com/ |
fd59384
to
6183101
Compare
btw the patch works for me, thank you for the work! |
/retest |
1 similar comment
/retest |
/retest |
Correctly validate crd.spec.versions
crd.spec.version got deprecated for crd.spec.versions
but in this case we are going to access a list of
dictionaries where the relevant value
is in the name field.
Fix all the validations on spec.versions and add
additional validations.
Fix also its test.
Signed-off-by: Simone Tiraboschi [email protected]
Fixes: #188