Closed IBims1NicerTobi closed 9 months ago
As I see from version 4.7.0 we can show the secret, so actually we can do the idempotency here. Before that it was too complex to see the secret.
So from 4.7.0 it's doable. For older version we have skip
and force
option and I'd leave it as is.
I'll look into it.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
containers.podman.podman_secret
fails if called twice with the same argumentsSteps to reproduce the issue:
Create a secret with containers.podman.podman_secret
Run the playbook again
Describe the results you received: The playbook fails with
fatal: [fishtank]: FAILED! => {"changed": false, "msg": "Unable to create secret: Error: test: secret name in use\n"}
Describe the results you expected: The playbook does nothing
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.):