Cherry-pick #19134 to 7.x: Fix tags for coredns/envoyproxy #19299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #19134 to 7.x branch. Original message:
What does this PR do?
When
{{ .tags }}
is evaluated in the module config it not written in the correct format.This fixes that issue and also conditionally enables
publisher_pipeline.disable_host
based on whether tags contains
forwarded
to be consistent with every other modulethat allows for
var.tags
to be set (relates: #13920).For example (https://play.golang.org/p/LUr-X94msd1):
will be written into the config as
which is a single value array containing the string "foo bar" rather than two tags.
Why is it important?
If a user specified more than one tag in a module config then they would not have had the expect tags in their events.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues