@ductape/mcp 0.1.11 → 0.1.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/dist/index.js +6 -3
  2. package/package.json +1 -1
  3. package/src/index.ts +6 -3
package/dist/index.js CHANGED
@@ -68,13 +68,16 @@ There are THREE categories of operations. Use the right tool for each:
68
68
  ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
69
69
  messageBroker, graph, vector, and any other resource with an envs array):
70
70
  The envs array MUST contain one entry for EVERY environment defined on the product.
71
- Omitting an env causes a validation error ("env X is not defined, please provide
72
- connection details"). You cannot scope an asset to a subset of environments.
71
+ import-persist and provision-persist enforce this with a preflight check: if the
72
+ generated draft does not cover all product environments the operation fails immediately
73
+ with error code MISSING_ENV_COVERAGE and a message listing exactly which envs are absent.
74
+ No creation or mutation is attempted. You cannot scope an asset to a subset of environments.
73
75
 
74
- BEFORE constructing any resource file:
76
+ BEFORE constructing any resource file or initiating import/provision:
75
77
  1. Run: ductape_cli("products environments list <product_tag> --json")
76
78
  2. Note every slug returned (e.g. dev, snd, prd).
77
79
  3. Collect connection details or confirmation for EACH slug from the user.
80
+ Do not proceed until you have details for every env.
78
81
 
79
82
  Sharing one resource across multiple envs is allowed but must be confirmed per env:
80
83
  - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ductape/mcp",
3
- "version": "0.1.11",
3
+ "version": "0.1.12",
4
4
  "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
package/src/index.ts CHANGED
@@ -79,13 +79,16 @@ There are THREE categories of operations. Use the right tool for each:
79
79
  ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
80
80
  messageBroker, graph, vector, and any other resource with an envs array):
81
81
  The envs array MUST contain one entry for EVERY environment defined on the product.
82
- Omitting an env causes a validation error ("env X is not defined, please provide
83
- connection details"). You cannot scope an asset to a subset of environments.
82
+ import-persist and provision-persist enforce this with a preflight check: if the
83
+ generated draft does not cover all product environments the operation fails immediately
84
+ with error code MISSING_ENV_COVERAGE and a message listing exactly which envs are absent.
85
+ No creation or mutation is attempted. You cannot scope an asset to a subset of environments.
84
86
 
85
- BEFORE constructing any resource file:
87
+ BEFORE constructing any resource file or initiating import/provision:
86
88
  1. Run: ductape_cli("products environments list <product_tag> --json")
87
89
  2. Note every slug returned (e.g. dev, snd, prd).
88
90
  3. Collect connection details or confirmation for EACH slug from the user.
91
+ Do not proceed until you have details for every env.
89
92
 
90
93
  Sharing one resource across multiple envs is allowed but must be confirmed per env:
91
94
  - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"