Improve LDAP password management #65
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.
Before the changes implemented in this PR, users were forced to include a block in their
vcfa_provider_ldaporvcfa_org_ldapdefinitions:With these changes, this requirement is no more. The idea is to save the LDAP password as the user provides it on create/update, ignoring the backend in this case (which never returns it). On reads, we just recover the value from state.
If the password is changed, the mechanism works exactly the same, so it detects password changes as normal.
Acceptance tests:
Manual checks:
vcfa_provider_ldapandvcfa_org_ldapHCL blocks. Apply as usual without anylifecyclemeta-argument.terraform plan. No updates-in-place should be reported.