Skip to content
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

client: log warning when SecureConfig is nil #207

Merged
merged 2 commits into from
Aug 18, 2022

Conversation

fairclothjm
Copy link
Contributor

so that it is obvious when looking back over the logs as to why your plugin checksum was not validated.

@fairclothjm fairclothjm merged commit f19a125 into master Aug 18, 2022
@fairclothjm fairclothjm deleted the log-secure-config-nil branch August 18, 2022 16:09
tgross added a commit that referenced this pull request Mar 1, 2023
In #207 we introduced a warning if the `SecureConfig` is unset. For Nomad and
other applications that have "internal" go-plugin consumers where the
application runs itself as a plugin, this causes spurious warn-level logs. For
Nomad in particular this means every task driver and logmon invocation emits the
log, which is our primary operation.

Setting a `SecureConfig` isn't required, and if a given go-plugin consumer
requires it to be, this seems more like a programming error than a runtime
error. Remove the log line.
tgross added a commit that referenced this pull request Mar 2, 2023
In #207 we introduced a warning if the `SecureConfig` is unset. For Nomad and
other applications that have "internal" go-plugin consumers where the
application runs itself as a plugin, this causes spurious warn-level logs. For
Nomad in particular this means every task driver and logmon invocation emits the
log, which is our primary operation.

Setting a `SecureConfig` isn't required, and if a given go-plugin consumer
requires it to be, this seems more like a programming error than a runtime
error. Remove the log line.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants