jenkins_script - Do not prevent username logging #34459
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Jenkins username used for HTTP request is obscured by
********
injenkins_script
output. This is problematic as valid username has a nonzero chance in appearing in script output that is therefore mangled.ISSUE TYPE
COMPONENT NAME
jenkins_script
ANSIBLE VERSION
ADDITIONAL INFORMATION
Username is not a secret as such so there is no need to obscure it. Sibling modules,
jenkins_job
andjenkins_plugin
, do not use it.