Skip to content

feat(ui): VM tags on the redesigned console (rebase of #256) - #260

Merged
Matheus-Thurler merged 4 commits into
mainfrom
feat/vm-tags-on-redesign
Oct 16, 2026
Merged

Matheus-Thurler merged 4 commits into
mainfrom
feat/vm-tags-on-redesign

Conversation

@Matheus-Thurler

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • go build ./... && go test ./...
  • npm run build e npm test (32 testes)
  • Revisão visual do wizard e do detalhe da VM em claro/escuro
  • Teste com os CRDs de operator#74 instalados

Add a Tags field to DeployVMInput and UpdateVMInput (nil means untouched,
a non-nil slice including an empty one replaces the tags), carry the tags
through DeployVM and UpdateVM, and persist them to Instance.spec.tags via
the store mapping. MergePlatformVM no longer resurrects cleared tags and
the legacy hypervisor deploy path forwards them too.
UpdateVM discarded the GetVM fallback result and re-queried the store,
which could return nil for legacy/KubeVirt-only VMs without an Instance
CR, panicking on the field access below. Use the GetVM result and add a
nil guard, with a regression test.
Show API tags in the VM list, seed the edit form with existing tags and
render them as removable pills (Enter/comma to add, Backspace to drop the
last). Extract a reusable TagsInput and reuse it in the deploy wizard,
fixing creation so more than one tag can be entered (the old input
stripped the comma on every keystroke). Add pt/en strings and a unit test
for mergeTags.
@Matheus-Thurler
Matheus-Thurler merged commit 7c60b1d into main Oct 16, 2026
8 checks passed
@Matheus-Thurler
Matheus-Thurler deleted the feat/vm-tags-on-redesign branch October 16, 2026 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants