-
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
Deprecate use_latest_spec
option
#14446
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
The |
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.
Nothing for docs to review
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.
nit - this should be changelog/fixed
as these files are shipped with the agent
I was on the fence with this one, as it technically doesn't change behaviour. But I'm also deferring this decision to what I mention in #14445's "Additional notes". |
70d3df2
to
6121ec6
Compare
3a46a08
to
5384d0a
Compare
The |
6121ec6
to
1abfce5
Compare
Hiding it because it should be no longer needed normally, now that we rely on the content type header to determine the incoming format.
5384d0a
to
b6abb6a
Compare
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.
🚀
What does this PR do?
Hides
use_latest_spec
option, as it's now left as a last resort in case the server exposing the metrics fails to set the appropiate header.Motivation
Follow-up.
Additional Notes
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attachedqa/skip-qa
label.