What does this MR do and why?

Updated usage


def test_vault_enabled(unit_is_enabled):
    """
    Check if the vault unit is enabled in the cluster.
    """
    assert unit_is_enabled("vault"), "Vault unit should be enabled in the cluster"

another solution is to provide the list of units per cluster, can be used like that:

def test_expected_units(enabled_units, logger):
    logger.info("Enabled units: %s", enabled_units)
    assert "vault" in enabled_units

Initial proposal

Add a generic fixture is_unit_enabled to check if a given unit is enable in the current cluster

Usage example:


def test_vault_enabled(is_unit_enabled):
    """
    Check if the vault unit is enabled in the cluster.
    """
    assert is_unit_enabled("vault"), "Vault unit should be enabled in the cluster"

another solution is to provide the list of units per cluster, can be used like that:

def test_expected_units(enabled_units_in_cluster, logger):
    logger.info("Enabled units: %s", enabled_units_in_cluster)
    assert "vault" in enabled_units_in_cluster

Test coverage

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 Jun 11, 2026 by Jonathan GAYVALLET

Sylva-test-framework: Add a generic fixture to check is a unit is enable in the cluster