fix: Use per-node shared flag for storage deduplication

The storage deduplication logic only checked cluster config's Shared
flag, but this required the cluster config API call to succeed. When
the per-node storage API already returns shared=1 (as the user
verified), we should use that directly.

Now we check three sources for shared storage detection:
1. Per-node API shared flag (storage.Shared)
2. Cluster config shared flag (if available)
3. Storage type heuristics (NFS, RBD, PBS, etc.)

Related to #1049
This commit is contained in:
rcourtman 2026-01-07 10:16:23 +00:00
parent dcdbee3c5c
commit 9cfcdbb247
18 changed files with 164 additions and 42 deletions

View file

@ -55,7 +55,7 @@ Because local login credentials are stored in `.env` (not part of exports), you
* If you used `.env`-based `API_TOKENS`/`API_TOKEN` (legacy), reconfigure them on the new host or re-create tokens in the UI.
3. **Update Agents**:
* **Unified Agent**: Update the `--token` flag in your service definition.
* **Docker**: Update `PULSE_TOKEN` in your container config.
* **Containerized agent**: Update `PULSE_TOKEN` in the agent container environment.
* *Tip: You can use the "Install New Agent" wizard to generate updated install commands.*
## 🔒 Security