Closed tinsjourney closed 11 months ago
This is a YAML thing, you use boolean and it's translated to Python True
. Just use quotes to make it string:
env:
BOOLEAN: 'true'
Thanks @sshnaidm didn't know about this YAML specificity.
Sorry for the noise, I close the issue
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When using module podman_container to create container, if in the env parameter we use a boolean (true/false), the container is created with the environment variable capitalized (True/False). Which can be an issue when you have script in your container looking for lowercase.
When creating container manually variable stay lowercase.
Steps to reproduce the issue:
Create playbook test.yaml
Execute playbook
Describe the results you received:
BOOLEAN variable is capitalized : True
Describe the results you expected:
BOOLEAN variable is lowercase as set in playbook : true
Additional information you deem important (e.g. issue happens only occasionally):
Version of the
containers.podman
collection: Either git commit if installed from git:git show --summary
Or version fromansible-galaxy
if installed from galaxy:ansible-galaxy collection list | grep containers.podman
Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbok you run with ansible (e.g. content of
playbook.yaml
):Command line and output of ansible run with high verbosity
Please NOTE: if you submit a bug about idempotency, run the playbook with
--diff
option, like:ansible-playbook -i inventory --diff -vv playbook.yml
Additional environment details (AWS, VirtualBox, physical, etc.):