-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix linter errors #302
Fix linter errors #302
Conversation
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'm concerned about secrets being leaked through errors and logs and the like.
Apart from that, though, overall good refactor. 👍
Hey @jlucktay, those are the names of the expected configuration key e.g. |
OK, good to know. Those variable names are really alarming in isolation. Even that comment makes me think twice:
To me, that reads like it's describing the secret itself, not the key to look up the secret in another thing somewhere else. |
Agreed, bad naming on my behalf. I'm going to leave as-is for now as I imagine this will all change when we move to goplugins anyway! |
The latest version of
golangci-lint
makes some critical changes to the linters, so I've fixed the various errors across multiple files.