fix: add no_log attribute to update_password variable - #26
Open
rvalab wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add
no_logattribute toupdate_passwordvariable to avoid warning from Ansible during execution.ISSUE TYPE
COMPONENT NAME
netapp.storagegrid.na_sg_org_user
ADDITIONAL INFORMATION
When using netapp.storagegrid.na_sg_org_user module, there is a warning displayed at every execution:
This is probably due to the name of the variable (
update_password).Ansible considers the variable contains sensitive data and expects to mark that variable with the
no_log: Trueattribute. (https://docs.ansible.com/ansible/latest/reference_appendices/logging.html)