vmware-aria 2.4.3__tar.gz → 2.4.4__tar.gz

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "vmware-aria",
   "displayName": "VMware Aria",
-  "version": "2.4.3",
+  "version": "2.4.4",
   "description": "VMware Aria Operations: metrics, alerts, capacity, anomaly detection — 46 MCP tools.",
   "author": {
     "name": "Wei Zhou",

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/.mcp.json

@@ -5,7 +5,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aria==2.4.3",
+        "vmware-aria==2.4.4",
         "vmware-aria-mcp"
       ]
     }

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: vmware-aria
-Version: 2.4.3
+Version: 2.4.4
 Summary: VMware Aria Operations (vRealize Operations) monitoring, alerting, and capacity planning
 Project-URL: Homepage, https://github.com/vmware-skills/VMware-Aria
 Project-URL: Repository, https://github.com/vmware-skills/VMware-Aria
@@ -39,6 +39,10 @@ AI-assisted monitoring and capacity planning for VMware Aria Operations (vRealiz
 [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
+MCP uses local stdio by default. Opt-in HTTPS opens the configured listener and requires TLS plus caller authentication; it is a network service, not a local-only mode. Credential examples create owner-only placeholder files without overwriting existing files; edit secrets locally.
+
+Container examples build a local version-tagged image and run it with `--pull=never`, avoiding registry fallback. A local version tag is not an immutable image digest.
+
 ## Upgrading to 2.0
 
 2.0 renames 4 of its MCP tools so every name starts with a verb (e.g. `findings_list` → `list_findings`, `fleet_certificate_list` → `list_fleet_certificates`, `fleet_domain_list` → `list_fleet_domains`). The full old → new table is in
@@ -72,7 +76,7 @@ against both the old and the new name, so one file serves both.
 
 ```bash
 # Install
-uv tool install vmware-aria
+uv tool install vmware-aria==2.4.4
 
 # Configure
 mkdir -p ~/.vmware-aria
@@ -88,13 +92,21 @@ default_target: prod
 EOF
 
 # Set password (never in config.yaml)
-echo "VMWARE_ARIA_PROD_PASSWORD=your_password" > ~/.vmware-aria/.env
-chmod 600 ~/.vmware-aria/.env
+(
+  umask 077
+  set -C  # Refuse existing files; edit an existing .env locally instead
+  cat > ~/.vmware-aria/.env <<'EOF'
+VMWARE_ARIA_PROD_PASSWORD=REPLACE_IN_LOCAL_EDITOR
+EOF
+)
+# Before continuing, edit .env locally; never type live secrets into shell commands.
 
 # Verify setup
 vmware-aria doctor
 ```
 
+This writes placeholders only. Enter passwords or tokens using a local editor after creation; do not paste live credentials into terminal commands, chat or commits. If the file exists, the command refuses to overwrite it; edit the existing file after checking its permissions are `600`.
+
 On macOS, v2.4.3 honors the system proxy bypass list for Aria targets. If an
 older installation reaches TCP/443 but token acquisition ends with a TLS close,
 upgrade and rerun `vmware-aria doctor`. `doctor --skip-auth` checks TCP only.
@@ -171,7 +183,7 @@ vmware-aria alert recommendations <alert-id>
 
 ## MCP Setup (Claude Code)
 
-After `uv tool install vmware-aria`, add to `~/.claude.json`:
+After `uv tool install vmware-aria==2.4.4`, add to `~/.claude.json`:
 
 ```json
 {
@@ -189,7 +201,7 @@ After `uv tool install vmware-aria`, add to `~/.claude.json`:
 
 > **v1.5.15+** uses the single-command form `vmware-aria mcp`. The legacy
 > `vmware-aria-mcp` console script is still kept for backward compatibility.
-> If you must use `uvx --from vmware-aria vmware-aria mcp` (no install) and hit
+> If you must use `uvx --from vmware-aria==2.4.4 vmware-aria mcp` (no install) and hit
 > `invalid peer certificate: UnknownIssuer` behind a corporate TLS proxy, set
 > `UV_NATIVE_TLS=true` or use the recommended `vmware-aria mcp` form above.
 

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/README-CN.md

@@ -9,6 +9,10 @@
 
 通过 Model Context Protocol (MCP) 为 VMware Aria Operations（原 vRealize Operations）提供 AI 辅助的监控与容量规划能力。
 
+MCP 默认使用本地 stdio。启用可选 HTTPS 后会打开配置的监听端口，并要求 TLS 与调用者认证；此时属于网络服务。凭据示例先创建仅当前用户可读写的占位文件，拒绝覆盖已有文件，再由用户在本地编辑秘密值。
+
+容器示例先在本地构建带版本标签的镜像，再用 `--pull=never` 运行，避免回退到镜像仓库拉取。本地版本标签不等于不可变的镜像摘要。
+
 ## 升级到 2.0
 
 2.0 把 MCP 工具名改成动词在前（共改名 4 处）（例如 `findings_list` → `list_findings`, `fleet_certificate_list` → `list_fleet_certificates`, `fleet_domain_list` → `list_fleet_domains`），完整的新旧名对照表见
@@ -40,7 +44,7 @@ vmware-policy ≥ 1.18 下仍然生效（`vmware-audit policy` 会列出因改
 
 ```bash
 # 安装
-uv tool install vmware-aria
+uv tool install vmware-aria==2.4.4
 
 # 配置
 mkdir -p ~/.vmware-aria
@@ -56,13 +60,21 @@ default_target: prod
 EOF
 
 # 设置密码（绝不存入 config.yaml）
-echo "VMWARE_ARIA_PROD_PASSWORD=your_password" > ~/.vmware-aria/.env
-chmod 600 ~/.vmware-aria/.env
+(
+  umask 077
+  set -C  # 拒绝覆盖已有文件；已有 .env 请直接用本地编辑器修改
+  cat > ~/.vmware-aria/.env <<'EOF'
+VMWARE_ARIA_PROD_PASSWORD=REPLACE_IN_LOCAL_EDITOR
+EOF
+)
+# 继续前，先用本地编辑器填写 .env；不要在终端命令中输入真实秘密值。
 
 # 验证配置
 vmware-aria doctor
 ```
 
+模板只写入占位符。创建后用本地编辑器填写密码或令牌；不要把真实凭据粘贴到终端命令、聊天或提交中。若文件已存在，上述命令会拒绝覆盖；直接编辑现有文件并先确认权限为 `600`。
+
 macOS 上的 v2.4.3 会遵守系统代理对 Aria 目标的绕过规则。如果旧版本能连通 TCP/443，
 但获取认证 token 时 TLS 连接被关闭，请升级后重新运行 `vmware-aria doctor`。
 `doctor --skip-auth` 只检查 TCP 连通性。
@@ -136,7 +148,7 @@ vmware-aria alert recommendations <alert-id>
 
 ## MCP 配置（Claude Code）
 
-完成 `uv tool install vmware-aria` 后，在 `~/.claude.json` 中添加：
+完成 `uv tool install vmware-aria==2.4.4` 后，在 `~/.claude.json` 中添加：
 
 ```json
 {
@@ -153,7 +165,7 @@ vmware-aria alert recommendations <alert-id>
 ```
 
 > **v1.5.15+** 推荐使用单命令 `vmware-aria mcp`。旧的 `vmware-aria-mcp` 入口仍然
-> 保留以向后兼容。如必须使用 `uvx --from vmware-aria vmware-aria mcp`（不安装）
+> 保留以向后兼容。如必须使用 `uvx --from vmware-aria==2.4.4 vmware-aria mcp`（不安装）
 > 且公司 TLS 代理报 `invalid peer certificate: UnknownIssuer`，请设置
 > `UV_NATIVE_TLS=true`，或直接使用上面的 `vmware-aria mcp` 形式。
 

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/README.md

@@ -14,6 +14,10 @@ AI-assisted monitoring and capacity planning for VMware Aria Operations (vRealiz
 [![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
+MCP uses local stdio by default. Opt-in HTTPS opens the configured listener and requires TLS plus caller authentication; it is a network service, not a local-only mode. Credential examples create owner-only placeholder files without overwriting existing files; edit secrets locally.
+
+Container examples build a local version-tagged image and run it with `--pull=never`, avoiding registry fallback. A local version tag is not an immutable image digest.
+
 ## Upgrading to 2.0
 
 2.0 renames 4 of its MCP tools so every name starts with a verb (e.g. `findings_list` → `list_findings`, `fleet_certificate_list` → `list_fleet_certificates`, `fleet_domain_list` → `list_fleet_domains`). The full old → new table is in
@@ -47,7 +51,7 @@ against both the old and the new name, so one file serves both.
 
 ```bash
 # Install
-uv tool install vmware-aria
+uv tool install vmware-aria==2.4.4
 
 # Configure
 mkdir -p ~/.vmware-aria
@@ -63,13 +67,21 @@ default_target: prod
 EOF
 
 # Set password (never in config.yaml)
-echo "VMWARE_ARIA_PROD_PASSWORD=your_password" > ~/.vmware-aria/.env
-chmod 600 ~/.vmware-aria/.env
+(
+  umask 077
+  set -C  # Refuse existing files; edit an existing .env locally instead
+  cat > ~/.vmware-aria/.env <<'EOF'
+VMWARE_ARIA_PROD_PASSWORD=REPLACE_IN_LOCAL_EDITOR
+EOF
+)
+# Before continuing, edit .env locally; never type live secrets into shell commands.
 
 # Verify setup
 vmware-aria doctor
 ```
 
+This writes placeholders only. Enter passwords or tokens using a local editor after creation; do not paste live credentials into terminal commands, chat or commits. If the file exists, the command refuses to overwrite it; edit the existing file after checking its permissions are `600`.
+
 On macOS, v2.4.3 honors the system proxy bypass list for Aria targets. If an
 older installation reaches TCP/443 but token acquisition ends with a TLS close,
 upgrade and rerun `vmware-aria doctor`. `doctor --skip-auth` checks TCP only.
@@ -146,7 +158,7 @@ vmware-aria alert recommendations <alert-id>
 
 ## MCP Setup (Claude Code)
 
-After `uv tool install vmware-aria`, add to `~/.claude.json`:
+After `uv tool install vmware-aria==2.4.4`, add to `~/.claude.json`:
 
 ```json
 {
@@ -164,7 +176,7 @@ After `uv tool install vmware-aria`, add to `~/.claude.json`:
 
 > **v1.5.15+** uses the single-command form `vmware-aria mcp`. The legacy
 > `vmware-aria-mcp` console script is still kept for backward compatibility.
-> If you must use `uvx --from vmware-aria vmware-aria mcp` (no install) and hit
+> If you must use `uvx --from vmware-aria==2.4.4 vmware-aria mcp` (no install) and hit
 > `invalid peer certificate: UnknownIssuer` behind a corporate TLS proxy, set
 > `UV_NATIVE_TLS=true` or use the recommended `vmware-aria mcp` form above.
 

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/RELEASE_NOTES.md

@@ -1,3 +1,16 @@
+## v2.4.4 — Security documentation and Gemini extension packaging
+
+Released 2026-11-09.
+
+Clarify actual capability, credential, local-write and transport boundaries where applicable.
+Pin documented setup/fallback tools and make credential examples owner-only before writing,
+without overwriting existing files. Runtime permissions, TLS defaults and approval behavior are unchanged.
+These edits do not establish a new ClawHub scan verdict.
+
+Add the root Gemini CLI extension manifest and discovery metadata, using the existing canonical skill and exact MCP package version. No duplicate skill entrypoint is introduced.
+
+Runtime infrastructure operations, permissions, TLS defaults and confirmation behavior are unchanged. No new vSphere/VCF 9.x or live product compatibility is claimed. ClawHub skill and bundle verdicts are checked separately after publication; documentation corrections are not a clean-scan claim.
+
 ## v2.4.3 — honor macOS proxy bypass for Aria targets (2026-11-08)
 
 * Update public author/project contact metadata to `zhouwei008@gmail.com`.
@@ -5,6 +18,7 @@
 * **Connection fix:** when macOS marks an Aria host as bypassed from its system HTTPS proxy, the HTTP client now uses a direct route for that host. It still honors CA bundle settings such as `SSL_CERT_FILE`; targets without a bypass keep their existing proxy route. Previously `httpx` picked up the proxy but missed the bypass, so token acquisition failed with a TLS connection close even though the appliance was healthy.
 * **Live verification on Aria Operations 8.18.7:** `get_aria_health` returned `HEALTHY`; resource and metric-key discovery succeeded. For a powered-on VM, 24-hour `cpu|usage_average` had 56 five-minute points and p95 44.154666900634766. The summary p95 exactly matched an independent nearest-rank calculation from the raw points. A powered-off VM had no CPU points and correctly reported `no_data_in_window`, not zero.
 
+
 ## v2.4.2 — p95 in metric summaries; the `confirmed` alias is gone; error hints fit the error (2026-11-01)
 
 * **Breaking for callers still sending `confirmed`:** the deprecated alias on `acknowledge_alert`, `cancel_alert`,

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/SECURITY.md

@@ -69,7 +69,7 @@ This skill makes no webhook, HTTP listener, or outbound network connections beyo
 This project is scanned with [Bandit](https://bandit.readthedocs.io/) before every release, targeting 0 Medium+ issues:
 
 ```bash
-uvx bandit -r vmware_aria/
+uvx bandit==1.9.4 -r vmware_aria/
 ```
 
 ## Supported Versions

vmware_aria-2.4.4/gemini-extension.json

@@ -0,0 +1,16 @@
+{
+  "name": "vmware-aria",
+  "version": "2.4.4",
+  "description": "VMware Aria Operations (vRealize Operations) monitoring, alerting, and capacity planning",
+  "mcpServers": {
+    "vmware-aria": {
+      "type": "stdio",
+      "command": "uvx",
+      "args": [
+        "--from",
+        "vmware-aria==2.4.4",
+        "vmware-aria-mcp"
+      ]
+    }
+  }
+}

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/openclaw.plugin.json

@@ -11,7 +11,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aria==2.4.3",
+        "vmware-aria==2.4.4",
         "vmware-aria-mcp"
       ]
     }

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zw008/vmware-aria",
-  "version": "2.4.3",
+  "version": "2.4.4",
   "description": "VMware Aria Operations: metrics, alerts, capacity, anomaly detection — 46 MCP tools.",
   "private": true,
   "license": "MIT",

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vmware-aria"
-version = "2.4.3"
+version = "2.4.4"
 description = "VMware Aria Operations (vRealize Operations) monitoring, alerting, and capacity planning"
 readme = "README.md"
 license = "MIT"

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/vmware-skills/VMware-Aria",
     "source": "github"
   },
-  "version": "2.4.3",
+  "version": "2.4.4",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "vmware-aria",
-      "version": "2.4.3",
+      "version": "2.4.4",
       "runtimeHint": "uvx",
       "packageArguments": [
         {

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/skills/vmware-aria/SKILL.md

@@ -16,7 +16,7 @@ compatibility: >
   vmware-policy auto-installed as Python dependency (provides @vmware_tool decorator and audit logging). All write operations audited to ~/.vmware/audit.db.
   Credentials: Each Aria Operations target requires a per-target password env var in ~/.vmware-aria/.env following the pattern VMWARE_ARIA_<TARGET_NAME_UPPER>_PASSWORD. Passwords are never logged or echoed.
   Read-heavy: 36 of 46 tools are read-only. Write operations limited to alert acknowledge/cancel, alert notes, alert definition management, report management, and resource maintenance start/end.
-  No webhooks, no outbound network calls, no guest operations. Local only: stdio MCP + Aria Operations REST API (HTTPS 443).
+  No webhooks or guest operations. API calls use the configured Aria endpoint (HTTPS 443); MCP defaults to stdio, with opt-in authenticated HTTPS.
   Transitive dependencies: Only vmware-policy (audit/policy). No post-install scripts or background services.
 ---
 
@@ -51,7 +51,7 @@ VMware Aria Operations (vRealize Operations 8.x, VCF Operations 9.x) AI-assisted
 ## Quick Install
 
 ```bash
-uv tool install vmware-aria==2.4.3
+uv tool install vmware-aria==2.4.4
 vmware-aria init      # guided setup: writes config + .env (chmod 600, password grep-safe), then verifies
 vmware-aria doctor
 ```
@@ -308,13 +308,13 @@ Set `VMWARE_ARIA_<TARGET_NAME_UPPER>_PASSWORD` (hyphens become underscores; targ
 
 ### `invalid peer certificate: UnknownIssuer` when running uvx (corporate TLS proxy)
 
-`uvx` re-resolves from PyPI on every launch, and a TLS-intercepting proxy breaks that. Run `vmware-aria mcp` after `uv tool install vmware-aria==2.4.3` (no network on launch), or set `UV_NATIVE_TLS=true` to use the system cert store.
+`uvx` re-resolves from PyPI on every launch, and a TLS-intercepting proxy breaks that. Run `vmware-aria mcp` after `uv tool install vmware-aria==2.4.4` (no network on launch), or set `UV_NATIVE_TLS=true` to use the system cert store.
 
 ## Audit & Safety
 
 1. **Source code**: [github.com/vmware-skills/VMware-Aria](https://github.com/vmware-skills/VMware-Aria) (MIT).
 2. **Config and credentials**: `config.yaml` holds hosts and usernames only; passwords live in `~/.vmware-aria/.env` (chmod 600) as `VMWARE_ARIA_<TARGET>_PASSWORD` and are never logged.
-3. **No webhooks**: no outbound calls besides the Aria Operations REST API over HTTPS 443; the MCP server is local stdio.
+3. **Network**: no webhooks. API calls use configured Aria HTTPS endpoints; MCP defaults to local stdio, with opt-in authenticated HTTPS.
 4. **TLS**: verification on by default; for a private CA set `SSL_CERT_FILE` rather than `verify_ssl: false` (isolated labs only).
 5. **Prompt-injection defense**: API text is sanitized (control characters stripped, length capped) before it reaches the agent.
 6. **Least privilege**: use an Aria Operations account with read-only roles unless the write tools (alert acknowledge/cancel, alert notes, alert definitions, reports, resource maintenance) are needed.

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/skills/vmware-aria/references/setup-guide.md

@@ -16,19 +16,19 @@ Complete setup and security guide for `vmware-aria`.
 ### Via uv (recommended)
 
 ```bash
-uv tool install vmware-aria==2.4.3
+uv tool install vmware-aria==2.4.4
 ```
 
 ### Via pip
 
 ```bash
-pip install vmware-aria==2.4.3
+pip install vmware-aria==2.4.4
 ```
 
 ### From source
 
 ```bash
-git clone --branch v2.4.3 https://github.com/vmware-skills/VMware-Aria.git
+git clone --branch v2.4.4 https://github.com/vmware-skills/VMware-Aria.git
 cd VMware-Aria
 pip install -e .
 ```
@@ -65,16 +65,21 @@ default_target: prod
 
 **Option A — .env file (recommended)**:
 ```bash
-cat > ~/.vmware-aria/.env << 'EOF'
-VMWARE_ARIA_PROD_PASSWORD=your_password_here
+(
+  umask 077
+  set -C  # Refuse existing files; edit an existing .env locally instead
+  cat > ~/.vmware-aria/.env <<'EOF'
+VMWARE_ARIA_PROD_PASSWORD=REPLACE_IN_LOCAL_EDITOR
 EOF
-chmod 600 ~/.vmware-aria/.env
+)
+# Before continuing, edit .env locally; never type live secrets into shell commands.
 ```
 
-**Option B — shell environment**:
-```bash
-export VMWARE_ARIA_PROD_PASSWORD=your_password_here
-```
+This writes placeholders only. Enter passwords or tokens using a local editor after creation; do not paste live credentials into terminal commands, chat or commits. If the file exists, the command refuses to overwrite it; edit the existing file after checking its permissions are `600`.
+
+**Option B — injected environment**: have your secret manager or launcher set
+`VMWARE_ARIA_PROD_PASSWORD` in the process environment. Do not type the secret in
+a terminal command or include it in MCP configuration committed to source control.
 
 Password variable naming convention: `VMWARE_ARIA_<TARGET_UPPER>_PASSWORD`
 - Target `prod` → `VMWARE_ARIA_PROD_PASSWORD`
@@ -194,7 +199,7 @@ Add to `~/.claude.json` (or use `claude mcp add`):
 
 > v1.5.15+ recommends `vmware-aria mcp`. Pre-1.5.15 used the legacy
 > `vmware-aria-mcp` console script (still kept for backward compatibility).
-> If using `uvx --from vmware-aria==2.4.3 vmware-aria mcp` and you hit
+> If using `uvx --from vmware-aria==2.4.4 vmware-aria mcp` and you hit
 > `invalid peer certificate: UnknownIssuer` behind a corporate TLS proxy,
 > set `UV_NATIVE_TLS=true` or use the recommended form above.
 
@@ -307,19 +312,19 @@ decide:
 ### Build and run
 
 ```bash
-docker build -t vmware-aria .
-docker run -i \
+docker build -t vmware-aria:2.4.4 .
+docker run --pull=never -i \
   -v ~/.vmware-aria:/root/.vmware-aria:ro \
   -e VMWARE_ARIA_CONFIG=/root/.vmware-aria/config.yaml \
-  vmware-aria
+  vmware-aria:2.4.4
 ```
 
+These commands run the image built locally above; `--pull=never` prevents a missing local image from falling back to a registry. The version tag identifies this build, not an immutable digest.
+
 ### Using docker-compose
 
 ```bash
-# Set password in your shell first
-export VMWARE_ARIA_PROD_PASSWORD=your_password
-
+# Inject VMWARE_ARIA_PROD_PASSWORD through your secret manager/launcher first.
 docker-compose up
 ```
 
@@ -361,7 +366,7 @@ Aria Operations Manager
 VMs / Hosts / Clusters / Datastores / Alerts / Capacity
 ```
 
-The MCP server uses stdio transport (local only, no network listener). Connections to Aria Ops use HTTPS on port 443 with vRealizeOpsToken authentication (6-hour sliding token validity, auto-refreshed).
+By default the MCP server uses local stdio without a listener; opt-in HTTPS opens a listener and requires TLS plus caller authentication. Connections to Aria Ops use HTTPS on port 443 with vRealizeOpsToken authentication (6-hour sliding token validity, auto-refreshed).
 
 ## Security Notes
 
@@ -371,7 +376,7 @@ The MCP server uses stdio transport (local only, no network listener). Connectio
 - **Never** store passwords in `config.yaml` — use env vars or `.env` file
 - `.env` file must be `chmod 600` (owner read/write only)
 - TLS verification is on by default (`verify_ssl: true`); trust a private CA with `SSL_CERT_FILE` rather than disabling verification (see [TLS Certificate Verification](#tls-certificate-verification))
-- The MCP server uses stdio transport — it runs locally only, no network listener
+- By default the MCP server uses local stdio without a listener. Opt-in HTTPS requires TLS plus caller authentication and opens the configured listener
 - Audit log at `~/.vmware/audit.db` (SQLite WAL, via vmware-policy) records all write operations (alert acknowledge/cancel, alert definition management, report generate/delete)
 - Tokens have a 6-hour sliding validity (extended on each call); the client re-acquires automatically 60 seconds before expiry. Requests carry `Authorization: vRealizeOpsToken <token>`
 

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/uv.lock

@@ -1,5 +1,5 @@
 version = 1
-revision = 3
+revision = 5
 requires-python = ">=3.10"
 resolution-markers = [
     "python_full_version >= '3.14' and sys_platform == 'win32'",
@@ -341,7 +341,7 @@ name = "exceptiongroup"
 version = "1.3.1"
 source = { registry = "https://pypi.org/simple" }
 dependencies = [
-    { name = "typing-extensions", marker = "python_full_version < '3.13'" },
+    { name = "typing-extensions" },
 ]
 sdist = { url = "https://files.pythonhosted.org/packages/50/79/66800aadf48771f6b62f7eb014e352e5d06856655206165d775e675a02c9/exceptiongroup-1.3.1.tar.gz", hash = "sha256:8b412432c6055b0b7d14c310000ae93352ed6754f70fa8f7c34141f91c4e3219", size = 30371, upload-time = "2025-11-21T23:01:54.787Z" }
 wheels = [
@@ -1142,7 +1142,7 @@ wheels = [
 
 [[package]]
 name = "vmware-aria"
-version = "2.4.3"
+version = "2.4.4"
 source = { editable = "." }
 dependencies = [
     { name = "httpx" },

{vmware_aria-2.4.3 → vmware_aria-2.4.4}/vmware_aria/__init__.py

@@ -1,3 +1,3 @@
 """VMware Aria Operations (vRealize Operations) monitoring and capacity planning."""
 
-__version__ = "2.4.3"
+__version__ = "2.4.4"