update: show node component versions in UI sidebar with hover details #81
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_compute!81
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_show_node_versions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
/versionendpoint returns structured JSON with all 5 component versions (hero_compute, my_hypervisor, hero_proc, cloud-hypervisor, mycelium)Changes
crates/hero_compute_ui/build.rs: Embed GIT_HASH at compile timecrates/hero_compute_ui/src/server.rs: Refactor version_handler to return structured component datacrates/hero_compute_ui/static/js/dashboard.js: Update version fetch and build component tooltipTest plan
Resolves #76
Good job, I think it might be better if we used a UI card that displays on hover instead of using the element title property, for example, see the status on the navbar
@ -0,0 +1,1032 @@---This file should not be committed
@ -1,4 +1,17 @@fn main() {// Embed git hash at compile time so it works in production (no .git dir).let git_hash = std::process::Command::new("git")Let's use a better way, i would suggest that we remove the hash since we already have the release version
2bcb414af7785fbe3212As we now have the central config, i would recommend that we use it to get the versions, no need for the hash
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.