-
Notifications
You must be signed in to change notification settings - Fork 77
confgenerator: omit semantic validation on user config #1081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
confgenerator/testdata/valid/linux/logging-custom_use_build_in_receivers/input.yaml
Outdated
Show resolved
Hide resolved
e10e141 to
07270ea
Compare
Signed-off-by: Ridwan Sharif <ridwanmsharif@google.com>
07270ea to
0fb4e36
Compare
confgenerator/confmerger.go
Outdated
|
|
||
| // Read the built-in config file. | ||
| original, err := builtInStruct.DeepCopy(platform) | ||
| template, err := builtInStruct.DeepCopy(platform) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Optional] I'd call this merged or result, FWIW. Eventually, we should probably turn mergeConfigs into a functional update (rather than in-place) and do the DeepCopy there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Naming is hard :(
I like the suggestion. Will attempt something in another PR so this doesn't block the release
Co-authored-by: igorpeshansky <igorpeshansky@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
The semantic validation should only happen on the merged config.
Related issue
http://b/267762522
How has this been tested?
Checklist: