Description
We should have the module pushed to the registry as the part of the release.
URL: europe-west3-docker.pkg.dev/sap-kyma-jellyfish-dev/template-operator:<version>
AC:
Reasons
For now we don't have this procedure automated or even described. When releasing a new template-operator version, module push has to be done manually. Many e2e/integration tests can be performance-optimized if we can use an already existing OCM artifact, instead of always building it locally. Besides that's the good test if our own tooling works as expected.
Description
We should have the module pushed to the registry as the part of the release.
URL:
europe-west3-docker.pkg.dev/sap-kyma-jellyfish-dev/template-operator:<version>AC:
modulectlandocmversions taken fromversions.yaml- preferably the same as in thelifecycle-managerReasons
For now we don't have this procedure automated or even described. When releasing a new template-operator version, module push has to be done manually. Many e2e/integration tests can be performance-optimized if we can use an already existing OCM artifact, instead of always building it locally. Besides that's the good test if our own tooling works as expected.