Skip to content

[Feature]: logger access and control #11

@ringerc

Description

@ringerc

Is there an existing issue already for this feature request/idea?

  • I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?

The plugin helper machinery hides the zap.Logger and all means of configuring it: It doesn't hook the Zap CLI options nor any env-vars. No means to control log format, json logging etc is provided.

There's only the plugin --debug flag.

Describe the solution you'd like

It would be helpful to be able to provide a plugin startup hook that can configure the logger etc, overriding the defaults here.

Otherwise each entrypoint into the plugin implementation has to reconfigure logging, and still can't influence the logging done by the helper itself.

Describe alternatives you've considered

I didn't really find any, since there doesn't seem to be a sensible means of unwrapping the logr.Logger to obtain the underlying zap root logger.

Additional context

No response

Are you willing to actively contribute to this feature?

No

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions