-
Notifications
You must be signed in to change notification settings - Fork 100
Make action optional when upgrade details are provided #5609
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
base: main
Are you sure you want to change the base?
Conversation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
…-server into fix/migrate-watching
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.
Sorry I am having trouble following how this PR works.
Does this fix the issue where if you check-in to a new cluster for the first time after migrate that it will reflect the upgrade state of that agent? If so, could you walk me through how this is done in this code.
action, err := ct.verifyActionExists(ctx, vSpan, agent, details) | ||
if err != nil { | ||
|
||
var actionTraceparent string |
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.
@blakerouse normally when no actin is present we stop here
but we make loading optional and if action is not present we just set traceparent (only property used here in the code) to ""
then later we check if we have here when setting parent span and continue until we reach a point where we update details on line 543
In a context of agent migration.
When agent is migrated and still has some upgrade details or upgrade was triggered manually for some reason we should reflect that in UI.
This PR makes action optional and updates upgrade details anyways.
I'd like ACK handling of upgrade to be reworked, but ideally in a separate PR to lower risk as I'd like this one to be in 9.2
Fixes: #5564