fix(DC): Bring EntityContainsColumnsValidator back to config entities #3579
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.
A repeat of #3540 but fixing two bad lines of code which should not have been merged
Due to a bug in our testing, we have not been including the EntityContainsColumnsValidator in the entities built with config. Having a place where the built in validators are defined makes it easier to auto-convert entities as we can skip the default ones in the config.
Blast Radius
This will affect only config entities (metrics) and this is re-introducing a columns validator which is turned off. This is essentially a no-op.