Exit earlier in error if OCI artifacts doesn't exist

Loic Nicollerequested to merge
early_fail_oci into main

What does this MR do and why?

Noticed by @mederic.deverdilhac in : https://gitlab.com/sylva-projects/sylva-core/-/jobs/7906059591#L80 when the OCI artifacts are not present we display a log message but we don't exit in error even if the deployment will fail later.

This MR ensure we exit as soon as we noticed the missing OCI

CI configuration

CI pipelines perform an update for both management and workload clusters, this update will NOT perform a ClusterAPI rolling update (deletion and creation of new K8s nodes) by default.

For some cases, it may be relevant to perform more complex tests.

Theses features can be activated in an MR by adding one of these labels to the MR and will apply to the next pipelines.

  • adding the label ci-featuretest-rolling-update pipelines will perform a node rolling update in the -update jobs (without version upgrades)
  • adding the label ci-featuretest-upgrade-from-1.1.1 pipelines will perform an upgrade from Sylva 1.1.1 to your dev branch (including a k8s version upgrade resulting in a node rolling update)

Merge request reports