vmware-aiops 2.3.2__tar.gz → 2.4.0__tar.gz

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "vmware-aiops",
   "displayName": "VMware AIops",
-  "version": "2.3.2",
+  "version": "2.4.0",
   "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "author": {
     "name": "Wei Zhou",

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/.mcp.json

@@ -5,7 +5,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aiops==2.3.2",
+        "vmware-aiops==2.4.0",
         "vmware-aiops-mcp"
       ]
     }

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: vmware-aiops
-Version: 2.3.2
+Version: 2.4.0
 Summary: VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool
 Project-URL: Homepage, https://github.com/vmware-skills/VMware-AIops
 Project-URL: Repository, https://github.com/vmware-skills/VMware-AIops
@@ -1204,6 +1204,7 @@ claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
   (default 2) sessions per target; each session is a login on the target, and a call waits at most 300 s for one.
 - **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
   nothing on the platform. Run one endpoint per privilege level.
+- **Several people or roles on one endpoint:** run `vmware-audit roles enable` once, then give each token a role (`vmware-audit token create NAME --role reader`, or a role in `roles.yaml` naming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
 
 **Offer only read tools, plus the writes you choose:**
 

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/README-CN.md

@@ -843,6 +843,7 @@ claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
   个会话；每个会话都是在该 target 上的一次登录，一个调用最多等待 300 秒拿到会话。
 - **能连到这个端点的人，都以该 server 配置的账号操作。** token 只用来识别调用者，不在平台上授予任何权限。
   每个权限级别单独起一个端点。
+- **一个端点给多人或多种角色用：** 先运行一次 `vmware-audit roles enable`，再给每个 token 指定角色（`vmware-audit token create 名字 --role reader`，或在 `roles.yaml` 里定义可用的工具和 target；需 vmware-policy ≥ 1.24.0）。角色只能限定这个 token 在本端点上能调用什么，不能超出账号本身的权限。详见 vmware-policy README 的「网络调用者的角色」一节。
 
 **只提供读工具，加上你选定的写工具：**
 

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/README.md

@@ -1180,6 +1180,7 @@ claude mcp add --transport http vmware-aiops https://mcp.example.com:8443/mcp \
   (default 2) sessions per target; each session is a login on the target, and a call waits at most 300 s for one.
 - **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
   nothing on the platform. Run one endpoint per privilege level.
+- **Several people or roles on one endpoint:** run `vmware-audit roles enable` once, then give each token a role (`vmware-audit token create NAME --role reader`, or a role in `roles.yaml` naming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
 
 **Offer only read tools, plus the writes you choose:**
 

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/RELEASE_NOTES.md

@@ -1,3 +1,12 @@
+## v2.4.0 — roles for network callers (HLD §18)
+
+* Declares the role metadata vmware-policy ≥ 1.24.0 needs to apply **roles** to this server over HTTPS
+  (HLD §18): how a missing target resolves, the guest and host-file tools that escape a role, and what each composite tool can run — `apply_vm_plan` and `rollback_vm_plan` reach every tool a plan step maps to plus `delete_vm` (rollback), `set_vm_ttl` reaches `delete_vm`, the batch tools reach the deploy and clone tools and the follow-up steps their arguments ask for (`reconfigure_vm`, `create_vm_snapshot`, `power_on_vm`, and `attach_iso_to_vm` for a deployment spec); a test derives these from what the batch code calls. A role may allow a composite only if it allows all of them. A test fails when a new plan action is not mapped to a tool. With an older vmware-policy nothing changes. Once an operator runs
+  `vmware-audit roles enable`, a token's role decides which tools and targets it may use here; a refused call is
+  audited as `denied`. See vmware-policy's README, "Roles for network callers".
+* A target-limited role is checked against the same config the connection uses: the copy the server's connection manager loaded on its first connection. Edit `config.yaml` and restart for both to see the change.
+* README and setup guide: one endpoint for several people or roles (run `vmware-audit roles enable` first).
+
 ## v2.3.2 — tools may not touch this server's own control files
 
 * **Security fix (HLD §18 step 0).** guest file download/upload, OVA and deployment-spec paths could name this server's own files, so over HTTPS a token holder could

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/openclaw.plugin.json

@@ -11,7 +11,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aiops==2.3.2",
+        "vmware-aiops==2.4.0",
         "vmware-aiops-mcp"
       ]
     }

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zw008/vmware-aiops",
-  "version": "2.3.2",
+  "version": "2.4.0",
   "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "private": true,
   "license": "MIT",

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vmware-aiops"
-version = "2.3.2"
+version = "2.4.0"
 description = "VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool"
 readme = "README.md"
 license = "MIT"

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/vmware-skills/VMware-AIops",
     "source": "github"
   },
-  "version": "2.3.2",
+  "version": "2.4.0",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "vmware-aiops",
-      "version": "2.3.2",
+      "version": "2.4.0",
       "runtimeHint": "uvx",
       "packageArguments": [
         {

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/skills/vmware-aiops/SKILL.md

@@ -63,7 +63,7 @@ Read before connecting an agent. Per-tool inventory: `references/capabilities.md
 ## Quick Install
 
 ```bash
-uv tool install vmware-aiops==2.3.2
+uv tool install vmware-aiops==2.4.0
 vmware-aiops doctor
 vmware-aiops hub status   # see which family members are installed
 ```
@@ -303,7 +303,7 @@ The account has no vSphere role. Assign one (Read-Only or higher) on the vCenter
 ## Setup
 
 ```bash
-uv tool install vmware-aiops==2.3.2
+uv tool install vmware-aiops==2.4.0
 mkdir -p ~/.vmware-aiops
 vmware-aiops init  # generates config.yaml and .env templates
 chmod 600 ~/.vmware-aiops/.env

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/skills/vmware-aiops/references/setup-guide.md

@@ -6,13 +6,13 @@ All install methods fetch from the same source: [github.com/vmware-skills/VMware
 
 ```bash
 # Via PyPI (recommended for version pinning)
-uv tool install vmware-aiops==2.3.2
+uv tool install vmware-aiops==2.4.0
 
 # Via Skills.sh (fetches from GitHub)
-npx skills add vmware-skills/VMware-AIops#v2.3.2
+npx skills add vmware-skills/VMware-AIops#v2.4.0
 
 # Via ClawHub (fetches from ClawHub registry snapshot of GitHub)
-clawhub install @zw008/vmware-aiops --version 2.3.2
+clawhub install @zw008/vmware-aiops --version 2.4.0
 ```
 
 ### Claude Code
@@ -35,7 +35,7 @@ claude mcp add vmware-aiops -- vmware-aiops mcp
 
 ```bash
 # 1. Install from PyPI (source: github.com/vmware-skills/VMware-AIops)
-uv tool install vmware-aiops==2.3.2
+uv tool install vmware-aiops==2.4.0
 
 # 2. Verify installation source
 vmware-aiops --version  # confirms installed version
@@ -73,7 +73,7 @@ The `vmware-aiops` package installs a Python CLI binary and its dependencies (py
 ## Development Install
 
 ```bash
-git clone --branch v2.3.2 https://github.com/vmware-skills/VMware-AIops.git
+git clone --branch v2.4.0 https://github.com/vmware-skills/VMware-AIops.git
 cd VMware-AIops
 uv venv && source .venv/bin/activate
 # --no-sources: pyproject's [tool.uv.sources] points vmware-monitor at a sibling
@@ -245,4 +245,5 @@ vmware-aiops mcp --transport https --host 0.0.0.0 --port 8443 \
 - **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
   nothing on the platform. Run one endpoint per privilege level (for example a read-only account behind
   `--expose read`, and a separate endpoint for operators).
+- **Several people or roles on one endpoint:** run `vmware-audit roles enable` once, then give each token a role (`vmware-audit token create NAME --role reader`, or a role in `roles.yaml` naming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
 

vmware_aiops-2.4.0/tests/test_policy_roles.py

@@ -0,0 +1,117 @@
+"""HLD §18 D-22: the role metadata this skill declares matches its real code."""
+
+from __future__ import annotations
+
+import asyncio
+
+import pytest
+
+from vmware_aiops import policy_roles
+from vmware_aiops.ops.plan_executor import dispatch_actions
+from vmware_aiops.ops.plan_gate import REFUSED_ACTIONS
+
+
+def _registry() -> set[str]:
+    from vmware_aiops.mcp_server.server import mcp
+
+    return {t.name for t in asyncio.run(mcp.list_tools())}
+
+
+@pytest.mark.unit
+def test_every_plan_action_is_mapped_or_refused():
+    """A new plan action must name the tool it amounts to, or a role could reach it unlisted."""
+    missing = dispatch_actions() - set(policy_roles.ACTION_TOOLS) - set(REFUSED_ACTIONS)
+    assert not missing, f"map these plan actions in policy_roles.ACTION_TOOLS: {sorted(missing)}"
+
+
+@pytest.mark.unit
+def test_every_declared_name_is_a_real_tool():
+    tools = _registry()
+    named = set(policy_roles.ESCAPES) | set(policy_roles.REACHES)
+    for reached in policy_roles.REACHES.values():
+        named |= reached
+    named |= set(policy_roles.ACTION_TOOLS.values())
+    assert named - tools == set(), sorted(named - tools)
+
+
+@pytest.mark.unit
+def test_plans_reach_delete_through_rollback():
+    assert "delete_vm" in policy_roles.REACHES["apply_vm_plan"]
+    assert "delete_vm" in policy_roles.REACHES["set_vm_ttl"]
+
+
+@pytest.mark.unit
+def test_metadata_is_declared_when_policy_has_roles():
+    roles = pytest.importorskip("vmware_policy.roles")
+    meta = roles.metadata("aiops")
+    assert meta is not None and meta.version == 1
+    assert meta.reaches["apply_vm_plan"] == policy_roles.REACHES["apply_vm_plan"]
+    assert "run_vm_guest_command" in meta.escapes
+
+
+#: ops function a batch calls → the tool that does the same thing alone.
+_OPS_TOOL = {
+    "clone_vm": "clone_vm",
+    "reconfigure_vm": "reconfigure_vm",
+    "create_snapshot": "create_vm_snapshot",
+    "power_on_vm": "power_on_vm",
+    "attach_iso": "attach_iso_to_vm",
+    "linked_clone": "deploy_linked_clone",
+    "deploy_from_template": "deploy_vm_from_template",
+    "deploy_ova": "deploy_vm_from_ova",
+    "create_vm": "create_vm",
+}
+
+#: batch tool → its ops function in vmware_aiops/ops/vm_deploy.py
+_BATCH_OPS = {
+    "batch_clone_vms": "batch_clone",
+    "batch_linked_clone_vms": "batch_linked_clone",
+    "batch_deploy_from_spec": "batch_deploy",
+}
+
+
+def _calls_in(func_name: str) -> set[str]:
+    import ast
+    import inspect
+
+    from vmware_aiops.ops import vm_deploy
+
+    tree = ast.parse(inspect.getsource(getattr(vm_deploy, func_name)))
+    return {
+        n.func.id if isinstance(n.func, ast.Name) else n.func.attr
+        for n in ast.walk(tree)
+        if isinstance(n, ast.Call) and isinstance(n.func, (ast.Name, ast.Attribute))
+    }
+
+
+@pytest.mark.unit
+@pytest.mark.parametrize("tool", sorted(_BATCH_OPS))
+def test_batch_reach_covers_every_step_it_runs(tool):
+    """Review M1: a batch that also reconfigures/snapshots/powers on reaches those tools."""
+    called = _calls_in(_BATCH_OPS[tool])
+    reached = {_OPS_TOOL[c] for c in called if c in _OPS_TOOL}
+    assert reached, f"{_BATCH_OPS[tool]} calls none of the known ops; update _OPS_TOOL"
+    assert reached <= policy_roles.REACHES[tool], sorted(reached - policy_roles.REACHES[tool])
+
+
+@pytest.mark.unit
+def test_the_resolver_uses_the_config_the_connection_manager_holds(monkeypatch):
+    """Review H1/H-1: once the server's connection manager exists, a config edit must
+    not move the role check off the config it connects with; before, read the file."""
+    import importlib
+    import types
+
+    from vmware_aiops import policy_roles as pr
+
+    server = importlib.import_module("vmware_aiops.mcp_server._shared")
+    assert hasattr(server, "_conn_mgr"), "policy_roles looks up a global the server does not have"
+    edited, loads = object(), []
+    monkeypatch.setattr(pr, "load_config", lambda: loads.append(1) or edited)
+
+    monkeypatch.setattr(server, "_conn_mgr", None)
+    assert pr._connection_config() is edited and pr._connection_config() is edited
+    assert len(loads) == 2  # no manager yet: the file as it is now, every time
+
+    held = object()
+    monkeypatch.setattr(server, "_conn_mgr", types.SimpleNamespace(_config=held))
+    assert pr._connection_config() is held  # the manager's copy, not the edited file

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/uv.lock

@@ -1195,7 +1195,7 @@ wheels = [
 
 [[package]]
 name = "vmware-aiops"
-version = "2.3.2"
+version = "2.4.0"
 source = { editable = "." }
 dependencies = [
     { name = "apscheduler" },
@@ -1240,7 +1240,7 @@ dev = [
 
 [[package]]
 name = "vmware-monitor"
-version = "2.3.1"
+version = "2.4.0"
 source = { editable = "../VMware-Monitor" }
 dependencies = [
     { name = "apscheduler" },
@@ -1276,14 +1276,14 @@ dev = [
 
 [[package]]
 name = "vmware-policy"
-version = "1.23.1"
+version = "1.24.0"
 source = { registry = "https://pypi.org/simple" }
 dependencies = [
     { name = "pyyaml" },
     { name = "rich" },
     { name = "typer" },
 ]
-sdist = { url = "https://files.pythonhosted.org/packages/ec/2c/03d2327478838ed3d407c7fc30ebbd6a2cf3b3d2c58285ba6653697224b0/vmware_policy-1.23.1.tar.gz", hash = "sha256:6fe55a99fc71f9591bedd3c5dcc00042559953f02a7bf7da9d2b9b4638877c08", size = 332522, upload-time = "2026-10-16T02:55:48.081Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/4a/62/3a3cb83af77e3dd3c8fc92cb3b7968bfda04a2f71bf0d6f9b72ee3198441/vmware_policy-1.24.0.tar.gz", hash = "sha256:fba12732ccbd4371232c15d9fd014f9f5d697497210aedff2515d1d205ed3577", size = 361302, upload-time = "2026-10-16T07:18:28.317Z" }
 wheels = [
-    { url = "https://files.pythonhosted.org/packages/b7/22/94fc30b3e273fd0e9739fb11ac0bfa8232352cefcaf95ee25229bb277733/vmware_policy-1.23.1-py3-none-any.whl", hash = "sha256:4afe95894e8a05556dfeb9e2c6a37186cf8c4bf3017131dedfb8c23478514cec", size = 114484, upload-time = "2026-10-16T02:55:46.591Z" },
+    { url = "https://files.pythonhosted.org/packages/3d/f2/fe3d9d384712023916e2cacddc385f14b095509c5e00aea417d1a9550e98/vmware_policy-1.24.0-py3-none-any.whl", hash = "sha256:cf615d0256134f01fb84c39b083649281a66d2c064c2eaa28786a0fa95ec6e58", size = 131460, upload-time = "2026-10-16T07:18:26.907Z" },
 ]

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/vmware_aiops/__init__.py

@@ -1,3 +1,3 @@
 """VMware AIops - AI-powered vCenter/ESXi monitoring and operations."""
 
-__version__ = "2.3.2"
+__version__ = "2.4.0"

{vmware_aiops-2.3.2 → vmware_aiops-2.4.0}/vmware_aiops/policy_environment.py

@@ -38,3 +38,6 @@ def _environment_for(target: str | None) -> str:
 # to ALLOW. Keyed, a resolver only ever answers for its own skill, so
 # registering at import time is safe again.
 set_environment_resolver(_environment_for, skill=skill_name(__name__))
+
+# Role metadata (HLD §18) is declared beside the environment resolver, on every surface.
+import vmware_aiops.policy_roles  # noqa: E402,F401

vmware_aiops-2.4.0/vmware_aiops/policy_roles.py

@@ -0,0 +1,123 @@
+"""What vmware-policy needs to apply roles to this skill (HLD §18 D-21/D-22).
+
+Policy cannot see which tools run other tools, which tools escape a role, or how a
+missing ``target`` resolves; this module declares them. Imported by
+``policy_environment``, so the MCP server and the CLI both register it. With a
+vmware-policy that has no roles module (< 1.24) nothing is declared.
+"""
+
+from __future__ import annotations
+
+import sys
+
+from vmware_policy import skill_name
+
+from vmware_aiops.config import load_config
+
+#: Each plan action → the tool that does the same thing. ``reset``/``suspend`` have no
+#: tool of their own; they change power state like ``power_off_vm``. The storage
+#: actions are refused by ``plan_gate.REFUSED_ACTIONS`` and are not listed.
+#: ``tests/test_policy_roles.py`` fails if a dispatch action is missing here.
+ACTION_TOOLS: dict[str, str] = {
+    "attach_iso": "attach_iso_to_vm",
+    "clone": "clone_vm",
+    "cluster_add_host": "add_cluster_host",
+    "cluster_remove_host": "remove_cluster_host",
+    "configure_cluster": "configure_cluster",
+    "convert_to_template": "convert_vm_to_template",
+    "create_cluster": "create_cluster",
+    "create_snapshot": "create_vm_snapshot",
+    "create_vm": "create_vm",
+    "delete_cluster": "delete_cluster",
+    "delete_snapshot": "delete_vm_snapshot",
+    "delete_vm": "delete_vm",
+    "deploy_ova": "deploy_vm_from_ova",
+    "deploy_template": "deploy_vm_from_template",
+    "guest_download": "download_vm_guest_file",
+    "guest_exec": "run_vm_guest_command",
+    "guest_upload": "upload_vm_guest_file",
+    "linked_clone": "deploy_linked_clone",
+    "migrate": "migrate_vm",
+    "power_off": "power_off_vm",
+    "power_on": "power_on_vm",
+    "reconfigure": "reconfigure_vm",
+    "reset": "power_off_vm",
+    "revert_snapshot": "revert_vm_snapshot",
+    "suspend": "power_off_vm",
+}
+
+#: A plan's rollback deletes VMs the plan created, so applying or rolling back a plan
+#: reaches ``delete_vm`` even when no step names it.
+_PLAN_REACHES = frozenset(ACTION_TOOLS.values()) | {"delete_vm"}
+
+REACHES: dict[str, frozenset[str]] = {
+    "apply_vm_plan": _PLAN_REACHES,
+    "rollback_vm_plan": _PLAN_REACHES,
+    "set_vm_ttl": frozenset({"delete_vm"}),  # the scheduler deletes later, with no caller
+    # The batch tools run the follow-up steps their arguments ask for (review M1).
+    "batch_clone_vms": frozenset(
+        {"clone_vm", "reconfigure_vm", "create_vm_snapshot", "power_on_vm"}
+    ),
+    "batch_linked_clone_vms": frozenset({"deploy_linked_clone"}),
+    "batch_deploy_from_spec": frozenset(
+        {
+            "deploy_vm_from_template",
+            "clone_vm",
+            "deploy_vm_from_ova",
+            "deploy_linked_clone",
+            "create_vm",
+            "reconfigure_vm",
+            "attach_iso_to_vm",
+            "create_vm_snapshot",
+            "power_on_vm",
+        }
+    ),
+    "restore_vm_clean_slate": frozenset({"power_off_vm", "revert_vm_snapshot"}),
+    "provision_vm_guest": frozenset({"run_vm_guest_command", "upload_vm_guest_file"}),
+}
+
+#: Tools that give their holder more than a role: code in a guest, files on the
+#: server host. (Host-path tools are added by policy while a file root is set.)
+ESCAPES = frozenset(
+    {
+        "run_vm_guest_command",
+        "run_vm_guest_command_with_output",
+        "upload_vm_guest_file",
+        "download_vm_guest_file",
+        "provision_vm_guest",
+    }
+)
+
+
+def _connection_config():
+    """The config the connection layer uses for this call (review H1, then H-1).
+
+    The server's connection manager loads the config once, on its first connection,
+    and keeps it. Once it exists, the role is checked against that same object, so
+    an edit to config.yaml cannot move the check off the target the call connects
+    to. Before it exists, the file as it is now is what the manager is about to load.
+    Looked up in ``sys.modules`` so the CLI never imports the MCP server.
+    """
+    server = sys.modules.get("vmware_aiops.mcp_server._shared")
+    manager = getattr(server, "_conn_mgr", None) if server is not None else None
+    return manager._config if manager is not None else load_config()
+
+
+def _target_name(target: str | None) -> str:
+    """The target the connection layer would use for ``target`` (or the default)."""
+    config = _connection_config()
+    return (config.get_target(target) if target else config.default_target).name
+
+
+try:
+    from vmware_policy.roles import declare_role_metadata
+except ImportError:  # vmware-policy without roles: nothing to declare
+    declare_role_metadata = None
+
+if declare_role_metadata is not None:
+    declare_role_metadata(
+        skill_name(__name__),
+        escapes=ESCAPES,
+        reaches=REACHES,
+        resolver=_target_name,
+    )