Added option to not removing $encrypted$ from filetree_create exported credentials #791
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.
What does this PR do?
Added option to not removing
$encrypted$
from filetree_create exported credentials. It keeps the$encrypted$
text, instead of `` empty string, in the credential files. It prevents the existing credential value from being overwritten with empty string if the configure files are being used as-is to import back into AAP.A condition is added to roles/filetree_create/templates/current_credentials.j2 to control the output.
How should this be tested?
Include
show_encrypted: true
in task invokingfiletree_create
Observe password fileds in output files
Is there a relevant Issue open for this?
resolves #788
Other Relevant info, PRs, etc
N/A