mcp-openstack-ops 3.5.9__tar.gz → 3.6.1__tar.gz

{mcp_openstack_ops-3.5.9 → mcp_openstack_ops-3.6.1}/.env.example

@@ -19,8 +19,9 @@ FASTMCP_TYPE=streamable-http
 FASTMCP_HOST=0.0.0.0
 FASTMCP_PORT=8000
 
-# (Optional) Enable authentication for streamable-http mode
-# Recommended for production environments
+# (Optional) Enable HTTP Bearer token authentication for streamable-http mode.
+# Clients must send Authorization: Bearer <REMOTE_SECRET_KEY> when enabled.
+# Recommended for production; use a strong, unique REMOTE_SECRET_KEY.
 REMOTE_AUTH_ENABLE=false
 REMOTE_SECRET_KEY=your-secure-secret-key-here
 

mcp_openstack_ops-3.6.1/.github/workflows/tests.yml

@@ -0,0 +1,28 @@
+name: Unit tests
+
+on:
+  push:
+    branches: ["main", "feat/73-per-user-connections"]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          fetch-depth: 0
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12.x"
+      - name: Install uv
+        run: pip install uv==0.7.20
+      - name: Install locked test dependencies
+        run: uv sync --locked --extra dev
+      - name: Run unit tests without cloud credentials
+        run: uv run --locked --extra dev python -m pytest -q tests

{mcp_openstack_ops-3.5.9 → mcp_openstack_ops-3.6.1}/.gitignore

@@ -17,4 +17,7 @@ wheels/
 
 .vscode*
 #.github/copilot-instructions.md
-*.swp
+*.swp
+
+# Windows download metadata
+*:Zone.Identifier

mcp_openstack_ops-3.6.1/AGENTS.md

@@ -0,0 +1,42 @@
+# Repository instructions
+
+These instructions supplement the user's global guidelines. They do not authorize
+Git writes, external publication, or changes to existing cloud resources.
+
+## Maintain the CLI-to-tool mapping and validation snapshot
+
+For every improvement or fix, review README.md's **OpenStack CLI vs MCP Tools
+Mapping** section. Keep its summary, tool rows, Status, Notes, and linked evidence
+consistent with the resulting implementation and actual verification.
+
+- Update affected rows whenever tools, actions, parameters, prerequisites,
+  permissions, limitations, or behavior change. Use registered tool names and
+  supported actions; do not advertise missing tools or unimplemented actions.
+- Distinguish implementation from verification. Mark implemented paths without
+  successful live validation as **Live unverified**, with the specific reason.
+  Missing services/APIs, policy denials, failures, and timeouts are not passes.
+  Keep intentional capability limitations and unimplemented actions explicit.
+- Keep **Live tool checks** and **Local unit tests** in separate summary groups.
+  Live classifications count unique tools; unit tests count test cases. Multiple
+  tests for one tool do not increase the unique-tool count. Keep classification
+  totals consistent with the stated inventory and scope.
+- Show unit-test results concisely as `160/160 (100%)`, using the actual results,
+  not this example's values. Account for failures and skipped tests separately
+  when present; do not count skipped tests as passes. Do not treat unit-test
+  success as proof of live service functionality.
+- Run relevant verification after functional changes. Update dates, source
+  revision or working-tree identity, counts, percentages, and evidence links only
+  from checks actually performed. Do not present an older snapshot as validation
+  of newer code. Mark affected paths as unverified or the snapshot as outdated
+  when validation cannot be repeated.
+- Replace a complete live summary only after repeating its stated coverage.
+  Label targeted retests as partial; do not extrapolate them to the full toolset.
+  Document polling limits and distinguish accepted requests from confirmed final
+  resource states. Explain changes in test conditions that affect comparisons.
+- Keep dated reports as historical evidence and link the latest applicable
+  report from README.md. Reports must state verification limits, observed
+  failures, and cleanup results without exposing credentials, private endpoints,
+  or sensitive resource data.
+- Before completion, check summary arithmetic, percentages, tool/action names,
+  Status/Notes, source identity, and evidence links for agreement. If README.ko.md
+  exists, maintain equivalent information in both README files.