Cherry-pick #20389 to 7.x: [Filebeat] Improve validation check for Azure configuration #20515
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 #20389 to 7.x branch. Original message:
What does this PR do?
An Azure blob container name must be between 3 and 63 characters in
length; start with a letter or number; and contain only letters,
numbers, and the hyphen. All letters used in blob container names must
be lowercase. Added validation to make sure the storage container
name meets those requirements.
Why is it important?
The default storage container name is made by appending "filebeat-" to
the eventhub name. But the eventhub name may contain invalid
characters or prepending "filebeat-" may make the name too long. If
either of those occur the user receives an error that the resource
name is invalid but no clear indication as to what is wrong or how to
fix. This validation will help guide the user to a valid storage
container name.
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Related issues