Emit warnings when conflicting configuration is specified #1506
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.
Depends on #1503
A warning mutator for when ineffective configuration pieces are specified.
Note: We do not give a warning when one of the conflicting value is nil. It already has a separate existing warning (#1329). If we wish to show conflict warnings for nil as well, we'll need to preserve nil values during normalization which is not the case today (code where we lose out on nil information during normalizaton:
cli/libs/dyn/convert/normalize.go
Line 248 in 533d357
What does the warning look like?