- Notifications
You must be signed in to change notification settings - Fork928
feat: use v2 API for agent lifecycle updates#12278
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
spikecurtis commentedFeb 23, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
This stack of pull requests is managed by Graphite.Learn more about stacking. Join@spikecurtis and the rest of your teammates on |
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.
Some tests need updating (relying on removedagentClient.PostLifecycle
), but otherwise LGTM!
agent/agent.go Outdated
lastReportedIndex++ | ||
continue | ||
} | ||
logger := a.logger.With(slog.F("payload", l)) |
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: Thepayload
should bepayload := &proto.UpdateLifecycleRequest{Lifecycle: l}
, as that's what's being sent.
0e7b180
to5586ecf
CompareThanks! Going to keep the PostLifecycle around, but deprecated so that we have tests against the v1 API. We can retire it all when we drop v1 support. |
5586ecf
toc17735d
CompareMerge activity
|
Uh oh!
There was an error while loading.Please reload this page.
Agent uses the v2 API to post lifecycle updates.
Part of#10534