sylva-units: don't require 'get-helm-version' named template to interpret the whole unit definition, 'helm_chart_versions' is sufficient (!9206) · Merge requests · Sylva-projects / sylva-core

In some situations (e.g. !8389 (closed)) we may need to have things in a unit definition depend on something that uses the get-helm-version named template to find what is the current version of a chart.

Today this can't work because we get a circular interpretation:

units.foo.helmrelease_spec.y.z uses _internal.foo_something
_internal.foo_something calls get-helm-version for unit foo
get-helm-version interprets units.foo
... ends up interpreting units.foo.helmrelease_spec.y.z
--> loop

To solve this this MR evolves get-helm-version so that it does not interpret anymore the whole unit definition, but will instead only interpret units.foo.helm_chart_versions.

A limitation remains, but a limitation which is intrinsic and minimal: helm_chart_versions of a given unit, can't make use of something that calls get-helm-version for the same unit. We can't do better than that since get-helm-version needs to use the interpreted content of helm_chart_versions.

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 Sep 17, 2026 by Thomas Morin

sylva-units: don't require 'get-helm-version' named template to interpret the whole unit definition, 'helm_chart_versions' is sufficient

CI configuration

Global config for deployment pipelines

Merge request reports