-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Rename cluster_name tag to envoy_cluster #9430
Conversation
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Docs review
Co-authored-by: ruthnaebeck <[email protected]>
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.
👍 for docs
Co-authored-by: Ofek Lev <[email protected]>
* Rename cluster_name tag to envoy_cluster * Sync models * Update envoy/assets/configuration/spec.yaml Co-authored-by: ruthnaebeck <[email protected]> * Sync config file * Apply suggestions from code review Co-authored-by: Ofek Lev <[email protected]> Co-authored-by: ruthnaebeck <[email protected]> Co-authored-by: Ofek Lev <[email protected]>
What does this PR do?
Rename tags:
cluster_name
->envoy_cluster
virtual_cluster_name
->virtual_envoy_cluster
with a configuration option for backward compatibility.
Same name as in spark config
integrations-core/spark/datadog_checks/spark/data/conf.yaml.example
Line 138 in 51a570a
Motivation
Additional Notes
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached