-
Notifications
You must be signed in to change notification settings - Fork 531
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
operator 3scale-community-operator (0.11.0) #4150
operator 3scale-community-operator (0.11.0) #4150
Conversation
Author of the PR is not listed as one of the reviewers in ci.yaml. Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions. |
Static test results
|
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.
wrong image references
- name: RELATED_IMAGE_APICAST
value: quay.io/3scale/3scale213:apicast-3scale-2.13.1-GA
- name: RELATED_IMAGE_SYSTEM
value: quay.io/3scale/3scale213:porta-3scale-2.13.1-GA
- name: RELATED_IMAGE_ZYNC
value: quay.io/3scale/3scale213:zync-3scale-2.13.1-GA
Pipeline SummaryPipeline: community-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/aba5577d3ba1a7feede9daf4e0b9ff64 TroubleshootingRun |
Author of the PR is not listed as one of the reviewers in ci.yaml. Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions. |
Static test results
|
Pipeline SummaryPipeline: community-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/5ec5fd9b3b7cbc78c7c9598bebae2261 TroubleshootingRun |
59b4814
to
10c2d3d
Compare
Pipeline SummaryPipeline: community-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/f77dede07604a131483b1cb4c367e0e2 TroubleshootingRun |
Thank you! Yes, it was draft. Now - updated. |
10c2d3d
to
703dc0f
Compare
hey @acornett21 @Allda Would it be possible to update the https://github.com/redhat-openshift-ecosystem/openshift-preflight/blob/53ba0b717599ec9c780df1c2ed31af9fef145467/internal/openshift/openshift.go#L240 to do some form of pre-validation of the catalog source name and add a prefix to it if it's not valid? I might be missing something but the pre-flight repository purpose seems to be for verification purposes, if the bundle is accepted it will be part of catalog source "community-operators" therefore I think we could maybe consider changing the catalog source name to some static value instead of adding a prefix/having it the same as package name. |
/pipeline restart operator-hosted-pipeline |
Author of the PR is not listed as one of the reviewers in ci.yaml. Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions. |
Static test results
|
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/60d226d05ed1e718944e1de85d715c0a TroubleshootingPlease refer to the troubleshooting guide. Run |
/pipeline restart operator-hosted-pipeline |
Author of the PR is not listed as one of the reviewers in ci.yaml. Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions. |
Static test results
|
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.
Operator bundle PR has been approved!
eb05497
into
redhat-openshift-ecosystem:main
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/6f8830a08850dc35ef924d3aa2290c88 TroubleshootingPlease refer to the troubleshooting guide. Run |
Pipeline SummaryPipeline: operator-release-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/05656fcad2809c7a824dec51bd0dd9ad TroubleshootingPlease refer to the troubleshooting guide. Run |
Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
Updates to existing Operators
Your submission should not
Operator Description must contain (in order)
Operator Metadata should contain
Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here