Skip to content

Ensure Kconfig-derived variables behind conditionals are exported and have role defaults #60

@dagomez137

Description

@dagomez137

Problem

Kconfig configuration options that are gated behind conditional logic are currently not exported into .extra_vars_auto.yamlextra_vars.yaml when using the output YAML option.

Reported-by: Chuck Lever <chuck.lever@oracle.com>
Link: https://lore.kernel.org/kdevops/60215220-9833-40d2-a29e-92a5917d20c2@oracle.com/

The extra_vars.yaml file is used as the execution environment for Ansible playbooks. If a variable is not present in this file and is also not defined in the corresponding role defaults (i.e. playbooks/roles/<role_name>/defaults/main.yml), then playbook execution may fail due to undefined variables. This creates failures when running playbooks outside the full kdevops environment, and reduces portability.

Task

Ensure that Kconfig-derived variables behind conditionals are still exported to .extra_vars_auto.yaml -> extra_vars.yaml.

Note

All Kconfig-derived variables must be defined in every role that uses them, following the same default value specified in Kconfig. If a role does not define a default for a variable it references, the default must be added to ensure portability of the playbook.

Link: https://lore.kernel.org/kdevops/20250924194212.323964-1-jlayton@kernel.org/
Link: https://lore.kernel.org/kdevops/75ab17ed-3ab6-4e43-b292-2521ad80865c@kernel.org/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions