Skip to content

Conversation

gzub-resonate
Copy link

Issue 780 - Add parameter to keep null or empty keys in taskdef

Added a new parameter called keep-null-value-keys which allows you to provide a csv separated list of keys which should not be dropped if they are empty, this is important for elements that have default values which are populated and you want to override them in the taskdef.

In our particular use case we wanted to override the tag parameter to be an empty string as in the splunk logging driver it defaults to a value "{{.ID}}", because of this default and the dropping of empty values this was not possible in the current version.

I added additional unit tests and verified that this action exhibits the correct behavior in our workflow.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@gzub-resonate gzub-resonate changed the title feature: adding keep-null-value-keys #780 feature: Add keep-null-value-keys parameter (Issue #780) Jul 31, 2025
@gzub-resonate
Copy link
Author

Any update on when this might get reviewed?

@gzub-resonate gzub-resonate changed the title feature: Add keep-null-value-keys parameter (Issue #780) feat: Add keep-null-value-keys parameter (Issue #780) Aug 18, 2025
@gzub-resonate
Copy link
Author

Can I get some more guidance on what is needed to help move this along... thanks!

@djglaser
Copy link

Hi @gzub-resonate, thank you for opening this PR. Our team will review it. In the meantime, can you please fix the failing build checks? Thank you!

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.

2 participants