-
Notifications
You must be signed in to change notification settings - Fork 18
Let the sensitive parts of credentials to be defined externally as variables #121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Let the sensitive parts of credentials to be defined externally as variables #121
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we add a changelog for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requires a changelog. Otherwise, I think this looks good
This is a new feature. I don't see what to specify into a changelog: https://docs.ansible.com/ansible-core/devel/dev_guide/testing/sanity/changelog.html |
aa919fa
to
6e1761e
Compare
I would probably make it a minor change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
e2372c3
to
cca8575
Compare
What does this PR do?
Let's the credentials and users (having sentitive data not exported by default) be used directly thanks to export the sensitiva data to external variables with a given syntax (see README.md for more details).
How should this be tested?
Manullay tested
Is there a relevant Issue open for this?
N/A
Other Relevant info, PRs, etc
N/A