fix: Add vault (secrets.yaml) support for existing passwords#449
Open
AmadeusPodvratnik wants to merge 1 commit intoIBM:mainfrom
Open
fix: Add vault (secrets.yaml) support for existing passwords#449AmadeusPodvratnik wants to merge 1 commit intoIBM:mainfrom
AmadeusPodvratnik wants to merge 1 commit intoIBM:mainfrom
Conversation
AmadeusPodvratnik
changed the title
Signed-off-by: Amadeuds Podvratnik <pod@de.ibm.com>
AmadeusPodvratnik
force-pushed
the
fix_issue_447
branch
from
b077666 to
dd95d85
Compare
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
1 participant
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.
Add ansible-vault support and add secrets.yaml template to secure the passwords accordingly.
The hosts file do not show passwords anymore.
In addition several lint issues where fixed, too (nevertheless there is still fixes to be done).
In addition the way how the RHEL subscription is be handled was extended to activation key and organization.
Tested with a HA KVM cluster (UPI installation).
This is the fix for issue #447