Skip to content
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

Merged
merged 64 commits into from Jan 26, 2024

Conversation

GustavoCaso
Copy link
Member

@GustavoCaso GustavoCaso commented Jan 23, 2024

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/templates folder.

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=systemd

Test that the agent status information gets appropriately displayed in the GUI agent launch-gui

Make sure to click in the general status and the collector tab to validate all information is being render properly

Reviewer's Checklist

  • If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
  • Use the major_change label 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.
  • A release note has been added or the changelog/no-changelog label has been applied.
  • Changed code has automated tests for its functionality.
  • Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
  • At least one team/.. label has been applied, indicating the team(s) that should QA this change.
  • If applicable, docs team has been notified or an issue has been opened on the documentation repo.
  • If applicable, the need-change/operator and need-change/helm labels have been applied.
  • If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
  • If applicable, the config template has been updated.

@GustavoCaso GustavoCaso force-pushed the render-agent-gui-status-using-status-component branch from d58aca1 to 70a7c58 Compare January 25, 2024 14:36
Base automatically changed from render-agent-status-using-status-component to main January 25, 2024 17:26
@dd-mergequeue dd-mergequeue bot requested review from a team as code owners January 25, 2024 17:26
@GustavoCaso
Copy link
Member Author

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.

@GustavoCaso GustavoCaso removed request for a team and dinooliva January 25, 2024 21:47
w.Header().Set("Content-Type", "text/html")
w.Write([]byte(html))
w.Write(stats)

Check warning

Code scanning / CodeQL

Reflected cross-site scripting Medium

Cross-site scripting vulnerability due to
user-provided value
.
@GustavoCaso
Copy link
Member Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Jan 26, 2024

🚂 MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 47m)

Use /merge -c to cancel this operation!

@dd-mergequeue dd-mergequeue bot merged commit d206d3b into main Jan 26, 2024
165 checks passed
@dd-mergequeue dd-mergequeue bot deleted the render-agent-gui-status-using-status-component branch January 26, 2024 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants