-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat: use Agent v2 API for Service Banner #11806
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
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @spikecurtis and the rest of your teammates on |
cfe6dcc to
6f243f6
Compare
368f754 to
4dc08bc
Compare
4dc08bc to
6e7e25f
Compare
6f243f6 to
a85394d
Compare
6e7e25f to
c4af306
Compare
a85394d to
1c21905
Compare
c4af306 to
4579eae
Compare
1c21905 to
98ab55e
Compare
4579eae to
7961d48
Compare
98ab55e to
174664c
Compare
7961d48 to
04cdbc1
Compare
174664c to
385e74a
Compare
04cdbc1 to
320f232
Compare
385e74a to
43a1c9e
Compare
320f232 to
492a7d4
Compare
| return c() | ||
| } | ||
|
|
||
| type FakeAgentAPI struct { |
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.
Could you generate this?
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.
I could generate it as a Mock, but that won't fit as easily into our existing tests.
492a7d4 to
a401924
Compare
Merge activity
|

Agent uses the v2 API for the service banner, rather than the v1 HTTP API.
One of several for #10534