Skip to content

Use remote CI values

Loic Nicolle requested to merge use_external_ci_values into main

What does this MR do and why?

  • Change our CI setup to use remote set of CI values
  • Remove environment-values/ci folder
  • Introduce a set of new variables to be able to configure from where we retrieve the values
  # Repo used to store CI values
  SYLVA_CI_VALUES_REPO: https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git
  SYLVA_CI_VALUES_FOLDER: environment-values/sylva-core-ci-values
  # Reference to checkout for CI values, by default we use the same for all stages but it can be overriden
  # eg: if we have a breaking change during an upgrade we could use a different branch for the deployment and update
  MGMT_INITIAL_CI_VALUES_REVISION: copy_sylva_core_values
  MGMT_UPDATE_CI_VALUES_REVISION: ${MGMT_INITIAL_CI_VALUES_REVISION}
  WC_INITIAL_CI_VALUES_REVISION: ${MGMT_INITIAL_CI_VALUES_REVISION}
  WC_UPDATE_CI_VALUES_REVISION: ${MGMT_INITIAL_CI_VALUES_REVISION}

by default we'll use the same reference for most of the cases, giving the ability to override it for a specific stages of the deployment will help in case where we have some breaking changes in our values so we could manage it via different branches in https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values.git repo instead of multiplying CI files

I kept the same structure of values in the remote repo to minimize the changes. I change the name of the folder to environment-values/sylva-core-ci-values to avoid potential conflict on old ref where environment-values/ci will still exist

the 2nd commits contain the changes made initially by @tmmorin in !2455 (closed) and adapted to match with the remote values setup

Related reference(s)

Need sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!2 (merged) to be merged (which includes !2455 (closed), so this MR here closes #1349 (closed))

close #1354 (closed)

Edited by Thomas Morin

Merge request reports