Cherry-pick #19587 to 7.x: Refuse invalid stream values in configuration #19866
Merged
michalpristas merged 1 commit intoelastic:7.xfrom Jul 14, 2020
Merged
Cherry-pick #19587 to 7.x: Refuse invalid stream values in configuration #19866michalpristas merged 1 commit intoelastic:7.xfrom
michalpristas merged 1 commit intoelastic:7.xfrom
Conversation
…ic#19587) * added stream check * changelog * fmt * invalid names * updated config files * updated config files * changes in all config files * config typo * small changes * Update go.sum
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
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
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 #19587 to 7.x branch. Original message:
What does this PR do?
Adds a filter which errors out when dataset.name or namespace is empty string.
Why is it important?
Described in #18772
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Fixes: #18772
Fixes: #17730