Cherry-pick #18890 to 7.x: Add check on <no value>
config option value for the azure input resource_manager_endpoint
#19352
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 #18890 to 7.x branch. Original message:
What does this PR do?
Adds a check on
<no value>
config option value for the azure inputresource_manager_endpoint
Updates test.
Why is it important?
Seems that after some recent changes, if a value is not set for
resource_manager_endpoint
then the value<no value>
is sent to the input config. This needs to be checked at the input level.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Do not set a value for
resource_manager_endpoint
when running the azure module in filebeat, no events will be generated and logs will provide more information on the error regarding the azure env.