We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rke2_config
Currently, when you utilize a templated variable within rke2_config, such as:
rke2_config: selinux: "{{ selinux_enabled }}"
Ansible will ultimately end up printing the literal string \"\{\{ selinux_enabled \}\}\" in the config.yaml file due to the way update_fact is used.
\"\{\{ selinux_enabled \}\}\"
config.yaml
update_fact
This is a known issue within ansible.utils and the best known resolution is to ensure the variable's values are rendered prior to use.
The text was updated successfully, but these errors were encountered:
rancherfederal#213 Render templated variables within rke2_config prio…
8fabeea
…r to updating
0777e6d
#215
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Description
Currently, when you utilize a templated variable within
rke2_config
, such as:Ansible will ultimately end up printing the literal string
\"\{\{ selinux_enabled \}\}\"
in theconfig.yaml
file due to the wayupdate_fact
is used.Additional Details
This is a known issue within ansible.utils and the best known resolution is to ensure the variable's values are rendered prior to use.
The text was updated successfully, but these errors were encountered: