Bug/fix credentials role ignoring update secrets #651
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.
What does this PR do?
Fix problem with credentials role always changing the secret even when 'update_secrets: false' is set. When evaluating the 'update_secrets' parameter, 'default' is forcing it to true when 'update_secrets' is set to false.
The normal behavior should not change the secret when user is setting 'update_secrets: false' and providing all required input matching the credential type.
The secret should only be changed when 'update_secrets' is set to true or not defined, and the credential inputs (except the secret value) are different from existing credential.
How should this be tested?
Explicitly setting controller_credentials variable like following with update_secrets as false
This always change the secret. Debugging shows the call to credential.py with update_secrets variable always set to true
Is there a relevant Issue open for this?
No
Other Relevant info, PRs, etc