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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor add_cloud_metadata to handle ECS fields easier #26438
Refactor add_cloud_metadata to handle ECS fields easier #26438
Changes from 1 commit
d187355
fbc9662
f5ee855
5310ef6
564d4d8
4e117f5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still seems that some special handling is done for
orchestrator
vscloud
fields. And it may be a bit confusing to have anout
, that is not an output of the function at the end.Wdyt about setting the orchestrator values directly on
meta
, so they don't have to be moved fromout
tometa
?And in the same way, perhaps
cloud
fields could be directly set onmeta["cloud"]
, so this intermediaryout
is not needed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼 Good point! I tried to get rid of the extra "cooking" and applied the schema for orchestrator fields on a different map, since unfortunately
Apply
cannot work in a "DeepUpdate
" way so it's not possible to write directly tocloud.*
in multiple places sincecloud*
will be overridden each timeApply
is called.