Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73391

Invoke Ansible Playbook extra variables values cannot be read

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • 2.452.2 LTS

      At some point it was decided that it's a terrific idea to encrypt values of keys in the Invoke Ansible Playbook extra variables section because some people apparently put passwords there without thinking much.
       
      Except that this makes it basically impossible to reconfigure or debug jobs using these variables, because you can't check what's their current values, and it's not always advisable to blindly enter something new there.
       
      Please revert this change or make it somehow optional for those of us who actually treat passwords with care because passwords are often being put in not very smart places in plain text and it doesn't mean everything should be encrypted and pain to use. There are multiple ways in Jenkins (and in Ansible itself) to safely store and use passwords, there's no need to cripple the job editing possibilities 

            Unassigned Unassigned
            kredens kredens
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: