Commits on Feb 1, 2024

1. Add optional spec.replaces field to CSV for update graph compliance …

   The way we generate our CSVs uses OLM's skipRange functionality. This is fine,
   but using only this leads to older versions becoming unavailable after the
   fact -- see the warning at [1].
   
   By adding an optional spec.replaces to our CSV we allow update testing as
   well as actual production updates for downstream builds that leverage it.
   
   Populating the field requires knowledge of the latest-released bundle,
   so we take it from an environment variable to be provided by the
   builder. If this is unset we don't include the spec.replaces field at
   all -- leaving previous behavior unchanged.
   
   Resolves #559
   Related: STF-1658
   
   [1] https://olm.operatorframework.io/docs/concepts/olm-architecture/operator-catalog/creating-an-update-graph/#skiprange
   
   (cherry picked from commit 99221fb)

   

   compi-migui committed Feb 1, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 1cffbb9
   • Browse repository at this point

   Copy the full SHA

   1cffbb9 View commit details

   Browse the repository at this point in the history