Skip to content

Conversation

@DeltaMichael
Copy link
Contributor

Why?

vdk_step_name and vdk_step_type were not filtered correctly when using json format

What?

Make sure the metadata filter alwats executes last, even when vdk_step_name and vdk_step_type are involved

Add separate functional test for vdk_step_name and vdk_step_type to avoid conflict with file_name in other tests

How was this tested?

Functional tests

What kind of change is this?

Feature/non-breaking

Why?

vdk_step_name and vdk_step_type were not filtered correctly when
using json format

What?

Make sure the metadata filter alwats executes last,
even when vdk_step_name and vdk_step_type are involved

Add separate functional test for vdk_step_name and vdk_step_type
to avoid conflict with file_name in other tests

How was this tested?

Functional tests

What kind of change is this?

Feature/non-breaking

Signed-off-by: Dilyan Marinov <mdilyan@vmware.com>
@DeltaMichael DeltaMichael force-pushed the person/mdilyan/filter-step-name-type branch from 2001da5 to dfa0ed2 Compare December 12, 2023 14:41
@DeltaMichael DeltaMichael merged commit 1d2bfba into main Dec 13, 2023
@DeltaMichael DeltaMichael deleted the person/mdilyan/filter-step-name-type branch December 13, 2023 09:19
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.

vdk-structlog: add vdk_step_name and vdk_step_type to tests and fix filtering bugs

5 participants