Invoke Ansible Playbook extra variables values cannot be read

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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Ā 

            Assignee:
            Unassigned
            Reporter:
            kredens
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: