-
Notifications
You must be signed in to change notification settings - Fork 83
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
fixed the secret resolver intialization #326
fixed the secret resolver intialization #326
Conversation
137df00
to
065aa5e
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #326 +/- ##
=======================================
Coverage 71.74% 71.74%
=======================================
Files 65 65
Lines 8723 8723
=======================================
Hits 6258 6258
Misses 2147 2147
Partials 318 318 ☔ View full report in Codecov by Sentry. |
log.Info("Initializing default secret resolver") | ||
secretResolver, err = resolver.NewDefaultResolver() | ||
} else { | ||
err = fmt.Errorf("unrecognized secret resolver type %v specified", secretResolverType) | ||
err = fmt.Errorf("unrecognized secret resolver type %v specified", admiralProfile) |
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.
err = fmt.Errorf("unrecognized admiral profile %v specified", admiralProfile)
Signed-off-by: Shriram Sharma <[email protected]>
Signed-off-by: Shriram Sharma <[email protected]>
Signed-off-by: Shriram Sharma <[email protected]>
e675eac
to
3969712
Compare
Thanks @shriramsharma for fixing this. |
Checklist
🚨 Please review this repository's contribution guidelines.
Description
What does this change do and why?
This fixed the default secret resolver intialization. It was broken during the merge.
[Link to related ISSUE]
Thank you!