chore(lua transform)!: use internally-tagged version enum for config rendering - #26097
Draft
thomasqueirozb wants to merge 1 commit into
Draft
chore(lua transform)!: use internally-tagged version enum for config rendering#26097thomasqueirozb wants to merge 1 commit into
thomasqueirozb wants to merge 1 commit into
Conversation
github-actions
Bot
added
docs review on hold
thomasqueirozb
changed the title
thomasqueirozb
added
the
meta: breaking change
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Restructure the
luatransform config into a proper internally-taggedversionenum so the generated docs mark version 2-only options (hooks,timers,metric_tag_values) withrelevant_when: version = "2".versionis now required, anddeny_unknown_fieldsis enforced (previously bypassed by the flattened versioned configs).Vector configuration
NA
How did you test this PR?
Ran the lua unit tests (39), the lua behavior tests, clippy, and regenerated the component docs.
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
NA