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
[ASCII-1024] Render agent gui status using status component #22287
[ASCII-1024] Render agent gui status using status component #22287
Conversation
d58aca1
to
70a7c58
Compare
|
Due to an issue merging the main back into this stacked PR, I carried over all the previous commits from #22115. That causes GH to assign new reviewers, but the actual file owners of the files modified on this PR already give the 👍. I will remove the ones added by GH because of the issue. |
|
/merge |
|
🚂 MergeQueue Pull request added to the queue. This build is going to start soon! (estimated merge in less than 47m) Use |
What does this PR do?
You can use the previous work done in #22115 and modify the GUI to use the status component for fetching and rendering the information.
With the help of the status component we no longer have to maintain the general and collector templates in the
cmd/agent/gui/views/templatesfolder.Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
PLEASE TAKE INTO CONSIDERATION THAT THE ORDER OF THE STATUS OUTPUT HAS CHANGED. When doing the QA, we need to focus on the same information being displayed and not too much on order.
Build the agent binary
invoke agent.build --build-exclude=systemdTest that the agent status information gets appropriately displayed in the GUI
agent launch-guiMake sure to click in the general status and the collector tab to validate all information is being render properly
Reviewer's Checklist
Triagemilestone is set.major_changelabel if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changeloglabel has been applied.qa/skip-qalabel, with required eitherqa/doneorqa/no-code-changelabels, are applied.team/..label has been applied, indicating the team(s) that should QA this change.need-change/operatorandneed-change/helmlabels have been applied.k8s/<min-version>label, indicating the lowest Kubernetes version compatible with this feature.