Invalidate cache if we encounter the old "sylva-toolbox-version" file in ensure_sylva_toolbox (!8038) · Merge requests · Sylva-projects / sylva-core

This MR fixes CI breakage that we still have around sylva-toolbox and gitlab CI runner file cache.

What seems to happen is that, even with the cache key scoped to a given branch (e.g. main), we still end up mixing versions because a CI run for a given branch (e.g. main), if the scenario is "sylva-upgrade" will first install the sylva-toolbox from release-1.6 (and hence put it in the cache).

The solution implemented here should ensure that code using the "old way" is never confused/mislead by code using the "new way":

the code using the "old way" will not mislead code using the "new way", because code using the "new way" is modified here to watch out for traces of the old sylva-toolbox-version file
the code using the "new way" will not keep the old sylva-toolbox-version on disk, and not mislead code using the "new way"

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited May 30, 2026 by Thomas Morin

Invalidate cache if we encounter the old "sylva-toolbox-version" file in ensure_sylva_toolbox

CI configuration

Global config for deployment pipelines

Merge request reports