Skip to content

chore: merge dev into main — main still calls backend routes deleted in backend-api#113 #97

Description

@pparage

main still contains the five DefaultVms composables that call bundle routes removed from the backend in range42-backend-api#113 (now merged to backend dev). They build their URLs dynamically, so a literal path grep does not find them:

  • src/composables/runnerCalls/bundle/core/proxmox/configure/DefaultVms/create.tsBUNDLE_PATH = '/v0/admin/run/bundles/core/proxmox/configure/default', then `${endpointBase.value}/create-vms-${target_infrastructure_group}`
  • .../DefaultVms/startStopPauseResumeVms.ts
  • .../DefaultVms/delete.ts
  • .../DefaultVms/snapshots/create.ts
  • .../DefaultVms/snapshots/revert.ts

All five are imported and instantiated by src/views/ProjectEditor.vue.

dev is already clean773539d removed the whole tree. This is purely a branch-sync gap: deploying a main UI against a dev backend gives 404s on those calls. In practice they were only wired to a global loading indicator whose triggers were never connected, so user-visible impact is likely nil — but the mismatch should not sit there.

The same five files are also present in all four git stash entries (stash@{0} on pr-43, stash@{1..3} on feature/gamenet-authoring-v1); worth dropping or rebasing those before they get restored onto a branch.

Sequence: merge deployer-ui devmain before any deploy that pairs a main UI with a dev backend.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions