Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: ansible-plugin, envinject-plugin
-
Labels:
-
Environment:Jenkins Version: 1.623
Ansible Plugin: 0.3.1
envinject: 1.91.4
mask-passwords: 2.7.4
OS:3.4.83-70.111.amzn1.x86_64
Ansible Version: 1.9.2
-
Similar Issues:
Description
I am unable to pass in a masked password as a variable via --extra-vars. I have tried using the EnvInject plugin and the Masked Password plugin to create the variable PASSWORD.
I then pass it in via
--etxra-vars="my_password=${PASSWORD}"
When I debug the ansible playbook instead of my_password being the masked value it is "*******".
It looks like the plugin does not attempt to unmask the variable before passing it to the playbook.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
I am unable to pass in a masked password as a variable via --extra-vars. I have tried using the EnvInject plugin and the Masked Password plugin to create the variable PASSWORD. I then pass it in via --etxra-vars="my_password=${PASSWORD}" When I debug the ansible playbook instead of my_password being the masked value it is "*******". It looks like the plugin does not attempt to unmask the variable before passing it to the playbook. |
I am unable to pass in a masked password as a variable via --extra-vars. I have tried using the EnvInject plugin and the Masked Password plugin to create the variable PASSWORD. I then pass it in via {noformat} --etxra-vars="my_password=${PASSWORD}" {noformat} When I debug the ansible playbook instead of my_password being the masked value it is "*******". It looks like the plugin does not attempt to unmask the variable before passing it to the playbook. |
Component/s | envinject-plugin [ 15893 ] | |
Component/s | ansible-plugin [ 20624 ] |
Labels | regression |
Component/s | ansible-plugin [ 20624 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Workflow | JNJira [ 164940 ] | JNJira + In-Review [ 197582 ] |
I came across the exact same issue, right at the same time. The only thing we had in common was the envinject pluging. I rolled it back to v1.90 and the problem is gone. That's a regression in that plugin, then.