Cherry-pick #20689 to 7.9: Rename cloud.provider to azure
instead of az
in add_cloud_metadata processor
#20823
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 #20689 to 7.9 branch. Original message:
What does this PR do?
Rename cloud.provider to
azure
instead ofaz
in add_cloud_metadataWhy is it important?
The cloud.provider's value is
az
but it is matched toazure
in theazure
module.Not sure why it is shorten
azure
toaz
. Looking around I do not see theaz
terminology being a popular one or even used anywhere (maybe in the az client). Unlikeaws
orgcp
,azure
is does not to abbreviate toaz
, using azure instead seems to me to be the most reasonable solution.Also, the elastic documentation shows that
azure
should be used instead.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues