Delete AlloyDB Omni operator #5925
Conversation
Signed-off-by: Jahnavi Malhotra [email protected] Co-authored-by: Manvi Gupta [email protected] Signed-off-by: Jahnavi Malhotra <[email protected]>
rh-operator-bundle-bot
added
operator-hosted-pipeline/passed
and removed
operator-hosted-pipeline/started
labels
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/3f01af0c3494baf3bfdf587326e852b0 TroubleshootingPlease refer to the troubleshooting guide. Run |
|
@jahnavi2k I see this is the second time this operator is being removed. Are you facing an issue with the workflow? |
rh-operator-bundle-bot
added
operator-release-pipeline/passed
and removed
operator-release-pipeline/started
labels
Pipeline SummaryPipeline: operator-release-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/b1f72511fdb4b7cad0f8cea0def62dc4 Release infoNothing was released. TroubleshootingPlease refer to the troubleshooting guide. Run |
|
Hi @mporrato Also, needed a small clarification: Any updates to an existing bundle except rollback isn't possible, even with FBC- enabled, right? Our change was failing the 'detect changes' test in the pipeline, that is why we had to completely rollback. |
|
What you can do with fbc enabled is remove the incorrect bundle and then add it back with the fix applied. It will involve two PRs, but at least it can be done in a self service fashion. |
|
So what we tried the last time was to remove the bundle from the catalogs as well as from the operators directory in a single PR. But the pipeline failed due to which we had to first remove it from the catalogs and then delete it with manual approval. Is there a better way that could have been handled or even now? Because without removing it from the catalogs, the pipeline fails. |
|
You're right. It will actually be 4 PRs: remove the bundle from the indices, remove the actual bundle, add it back and update the indices again. We are working on making it possible to change indices and a bundle in a single PRs but this is not ready yet. |
|
Got it, thank you so much for the insights and help! |
Signed-off-by: Jahnavi Malhotra [email protected]
Co-authored-by: Manvi Gupta [email protected]
Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions
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