f30862f3c0
The API token was previously stored only in storage.cfg, which is replicated in plaintext across all cluster nodes via pmxcfs. This adds a keyfile mechanism: at startup each public entry point calls _resolve_token(), which checks /etc/pve/priv/truenas-<storeid>.key before falling back to truenas_api_key in storage.cfg. The resolved token is cached in the per-host $state so the file is read at most once per daemon session. truenas_api_key is now optional in storage.cfg; either the keyfile or the config key must be present. Docs updated in getting-started.md (section 4.1) and the in-app help HTML with setup commands and the cluster-copy reminder. Closes #261 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| TrueNAS.pm | ||