Allow admins to create and reassign containers for other users

[Copilot]

Admins can now create containers attributed to other users (or reassign ownership of existing containers) by passing username in the request body. API-only — no UI changes.

Changes

• POST /sites/:siteId/containers — admins may pass username to set the container owner to a different user (validated against the Users table; 404 if not found). Non-admins continue to own their own containers.
• PUT /sites/:siteId/containers/:id — admins may pass username to reassign container ownership. Only updates if the username differs from the current owner.
• User model imported in containers.js for pre-insert existence checks.
• OpenAPI spec updated with username field on both endpoints, marked admin-only.

Example

POST /api/v1/sites/1/containers
Authorization: ******

{
  "hostname": "my-container",
  "template": "ubuntu:22.04",
  "username": "alice"
}

PUT /api/v1/sites/1/containers/42
Authorization: ******

{
  "username": "bob"
}

[runleveldev]

@copilot

[Copilot]

Pull request overview

This PR extends the containers API to let admins (only) set or change a container’s owner by passing a username in the request body, and documents the new field in the OpenAPI spec.

Changes:

• Added username request-body support to POST /sites/:siteId/containers to create containers on behalf of another user.
• Added username request-body support to PUT /sites/:siteId/containers/:id to reassign container ownership (only when changed).
• Updated openapi.v1.yaml to document the new username field and related 403 behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
create-a-container/routers/api/v1/containers.js	Adds request parsing and ownership assignment/reassignment via optional username.
create-a-container/openapi.v1.yaml	Documents username on create/update container endpoints and updates 403 responses accordingly.

[cmyers-mieweb]

We still leave tags depending on the owner of the container, if we want to still be consistent we will need to make a call to the Proxmox API to update the tag to the new container owner.

[runleveldev]

We still leave tags depending on the owner of the container, if we want to still be consistent we will need to make a call to the Proxmox API to update the tag to the new container owner.

@copilot

[Copilot]

We still leave tags depending on the owner of the container, if we want to still be consistent we will need to make a call to the Proxmox API to update the tag to the new container owner.
<img al...

The PUT handler now pushes the new owner as the Proxmox tag (updateLxcConfig with tags: newOwnerUsername) whenever ownership is reassigned and the container has a VMID. It's best-effort like the delete path — a node-API failure is logged rather than failing the request. Commit: 2767949