-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Question
I am not sure whether this is a bug or I am doing something wrong. I have used Semaphore 2.8 for quite a time and all of my playbooks worked fine. I am mainly doing netconf Juniper/Cisco stuff with it and I always had my login credentials (login with password) in the Semaphore key store.
However, after updating from 2.8 to 2.17, I got "authentication errors" on my playbooks. I did a little bit of digging and found out that all of my playbooks are executed with the --ask-pass parameter, my key store entry was completely ignored. I tried to delete my entry and re-create it but the issue was still the same.
I did a workaround with environments to store the password there. But I would like to find out the issue or if that's maybe intentional.
Related to
Ansible (task execution)