Long term support for olm.substitutesFor annotation

[p.g.ric...@phantomjinx.co.uk]

Hi,

Our project (camel-k) has been trying to overcome difficulties with image respins of our product. Until now, we had been trying to do it by substituting the replaces property in the OLM CSV. However, we have only just found out today that not only does the olm.substitutes annotation exist but that it is also supported by our internal build systems. Therefore, it seems to be just what we need to solve our problem.

In doing the investigation, we came across issue #782 (Deprecate substitute-for field in the CSV). Obviously, we have a bit of work to migrate to this property but just want to check on its long-term viability seeing as its not clear as to whether it will be deprecated, please?

Thanks

Paul Richardson (Red Hat)

[Lance Galletti]

The field will be deprecated. An identical feature (and more) is available with the use of File-Base Catalogs (a declarative api for update graph management).

--
You received this message because you are subscribed to the Google Groups "operator-framework-olm-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to operator-framework-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/operator-framework-olm-dev/1751fc72-1b4c-49b1-b540-87c220ae1e43n%40googlegroups.com.

--

Lance Galletti

He / Him / His

Senior Software Engineer

OpenShift