Skip to content

Conversation

@DeltaMichael
Copy link
Contributor

Why?

vdk-structlog has a default config flag set to True when installed. It relegates all logging configuration to the plugin and is checked in core, i.e. if structlog is installed, vdk will use structlog. If it's not installed, it will use the configuration available in core. The flag is currently checked using an env variable, which makes it not work.

What?

Check the flag using the config object

How was this tested?

Manually

What kind of change is this?

Bugfix

Why?

vdk-structlog has a default config flag set to True when installed.
It relegates all logging configuration to the plugin and is cheked in core,
i.e. if structlog is installed, vdk will use structlog. If it's not installed,
it will use the configuration available in core. The flag is currently checked
using an env variable, which makes it not work.

What?

Check the flag using the config object

How was this tested?

Manually

What kind of change is this?

Bugfix

Signed-off-by: Dilyan Marinov <mdilyan@vmware.com>
@DeltaMichael DeltaMichael merged commit a4c5a23 into main Feb 15, 2024
@DeltaMichael DeltaMichael deleted the person/mdilyan/enable-disable-structlog branch February 15, 2024 07:32
yonitoo pushed a commit that referenced this pull request Feb 15, 2024
## Why?

vdk-structlog has a default config flag set to True when installed. It
relegates all logging configuration to the plugin and is checked in
core, i.e. if structlog is installed, vdk will use structlog. If it's
not installed, it will use the configuration available in core. The flag
is currently checked using an env variable, which makes it not work.

## What?

Check the flag using the config object

## How was this tested?

Manually

## What kind of change is this?

Bugfix

Signed-off-by: Dilyan Marinov <mdilyan@vmware.com>
Co-authored-by: Dilyan Marinov <mdilyan@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants