add deprication warning for operator version 1.0.0 #66
Conversation
There was a problem hiding this comment.
I'm not sure this is done correctly, I think you need to add something like this (not sure if the wording is correct or I missed something)
---
schema: olm.deprecations
package: rhtas-operator
entries:
- reference:
schema: olm.channel
name: stable-v1.0
message: channel stable-v1.0 is no longer supported. Please switch to channel 'stable' or channel 'stable-v1.1'.
- reference:
schema: olm.bundle
name: rhtas-operator.v1.0.0
message: rhtas-operator.v1.0.0 is deprecated. Uninstall and install rhtas-operator.v1.1.0 for support.
- reference:
schema: olm.bundle
name: rhtas-operator.v1.0.1
message: rhtas-operator.v1.0.1 is deprecated. Uninstall and install rhtas-operator.v1.1.0 for support.
- reference:
schema: olm.bundle
name: rhtas-operator.v1.0.2
message: rhtas-operator.v1.0.2 is deprecated. Uninstall and install rhtas-operator.v1.1.0 for support.
---
to each of the graph.yaml files then you can re render the catalog.json with opm
Screencast.from.2025-01-08.12-11-03.mp4This is what it will look like :) |
Signed-off-by: Janine Olear <pninak@web.de>
miyunari
force-pushed
the
feat/operator_deprication_message
branch
from
b1450c2 to
61b6963
Compare
|
Thank you for the great description @JasonPowr and the video ❤️ ! I changed it to what you've suggested, please double check again if it makes sense now 😄 |
v4.13/graph.yaml
Outdated
| - reference: | ||
| schema: olm.bundle | ||
| name: rhtas-operator.v1.0.1 | ||
| message: rhtas-operator.v1.0.1 is deprecated. Uninstall and install rhtas-operator.v1.1.0 for support. |
There was a problem hiding this comment.
| message: rhtas-operator.v1.0.1 is deprecated. Uninstall and install rhtas-operator.v1.1.0 for support. | |
| message: rhtas-operator.v1.0.1 is deprecated. Uninstall and install rhtas-operator.v1.1.1 for support. |
I think we should change this as 1.1.1 will be the latest version of the operator
There was a problem hiding this comment.
Haha yes, good point 😅
| "name": "rhtas-operator.v1.0.0", | ||
| "message": "This version is deprecated. Please upgrade to rhtas-operator.v1.1.0." |
There was a problem hiding this comment.
Please correct me if I am wrong, but I believe you are making these changes manually ?, The catalog.json file is something that is generated using the opm tool, you can find more info here in the FBC bits
There was a problem hiding this comment.
yes, I did these changes manually 😄 I changed it now :)
|
I used the opm tool now to generate the |
JasonPowr
left a comment
JasonPowr
left a comment
There was a problem hiding this comment.
Just this one thing related to the related images sections of the catalog.json and your good to go :)
| { | ||
| "name": "", | ||
| "image": "registry.redhat.io/rhtas/rhtas-rhel9-operator@sha256:2d2a22420249890a64b42c663d57c4b5c6638e0597fe74b01b275ba915e53ea2" | ||
| }, |
There was a problem hiding this comment.
Some of these related images have been deleted, for this issue the only change made to the catalog.json file should be the addition of the olm.deprecations :)
There was a problem hiding this comment.
oh no - I didn't see that 👍 I will change it in a bit :)
Signed-off-by: Janine Olear <pninak@web.de>
miyunari
force-pushed
the
feat/operator_deprication_message
branch
from
c304afc to
9632324
Compare
2 participants
Updated the
operator catalogwith deprecation warnings:Deprecation warning for
operator-v1.0.0:Added a message recommending users to upgrade to
operator-v1.1.0for continued support.Deprecation warning for
stable-v1.0 channel:Added a message recommending users to switch to the newer
stable-v1.1channel.I used this schema.