-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
feat(config): add diff with remotes for auth #2814
base: develop
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 11626956411Details
💛 - Coveralls |
result.Email.Smtp.Host = *remoteConfig.SmtpHost | ||
} | ||
if remoteConfig.SmtpPass != nil { | ||
result.Email.Smtp.Pass = *remoteConfig.SmtpPass |
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.
I think this value is masked in api response.
6ebd353
to
d115c28
Compare
return | ||
} | ||
localHashed := sha256Hmac(secret, *local) | ||
diff.CompareSensitiveField(&localHashed, remote) |
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.
remark
Here I still use CompareSentitiveField
to keep a human readable result message. We could just use the standard comparaison over the hashed values but I think that might confuse the users wondering why the value they set in their config get a different value in their config diff.
What kind of change does this PR introduce?
feature
relates to #2552
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.