@ductape/mcp 0.1.12 → 0.1.13

package/dist/index.js

@@ -68,10 +68,11 @@ There are THREE categories of operations. Use the right tool for each:
        ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
        messageBroker, graph, vector, and any other resource with an envs array):
        The envs array MUST contain one entry for EVERY environment defined on the product.
-       import-persist and provision-persist enforce this with a preflight check: if the
-       generated draft does not cover all product environments the operation fails immediately
-       with error code MISSING_ENV_COVERAGE and a message listing exactly which envs are absent.
-       No creation or mutation is attempted. You cannot scope an asset to a subset of environments.
+       import-persist and provision-persist only generate a draft for ONE env at a time.
+       Calling import-persist once will fail with MISSING_ENV_COVERAGE because the single-env
+       draft does not cover all product environments. Use import-persist-all or
+       provision-persist-all instead — they accept an array of per-env inputs, import/provision
+       each env in parallel, merge the drafts, and persist once with full env coverage.
 
        BEFORE constructing any resource file or initiating import/provision:
          1. Run: ductape_cli("products environments list <product_tag> --json")
@@ -79,6 +80,16 @@ There are THREE categories of operations. Use the right tool for each:
          3. Collect connection details or confirmation for EACH slug from the user.
             Do not proceed until you have details for every env.
 
+       Use import-persist-all / provision-persist-all (not the single-env forms) whenever
+       you have details for all envs. The file must be a JSON array — one object per env,
+       same format as a single import-persist/provision-persist input, all sharing the same
+       product and component tag. Example:
+         [{"cloud":"gcp-snd","service":"gcs","type":"storage","product":"my-prod",
+           "component":"assets","env":"snd","resource":"snd-bucket"},
+          {"cloud":"gcp-prd","service":"gcs","type":"storage","product":"my-prod",
+           "component":"assets","env":"prd","resource":"prd-bucket"}]
+         → ductape_cli("cloud resources import-persist-all -f all-envs.json --json")
+
        Sharing one resource across multiple envs is allowed but must be confirmed per env:
          - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
          - Never assume shared configuration without confirmation.
@@ -1163,27 +1174,38 @@ async function main() {
                 '         resources storage create -f storage.json\n' +
                 '       File shape: { name, tag, envs: [{ slug, type: "aws"|"gcp"|"azure", config: { bucketName, ...creds } }] }\n' +
                 '       For cloud-linked envs set config.cloud to the connection tag and omit raw credentials.\n' +
-                '    2. Import an existing cloud bucket via a cloud connection (no provisioning):\n' +
-                '         cloud resources import-persist -f import.json --json\n' +
-                '       File requires: cloud (connection tag), service (e.g. "gcs","s3"), type ("storage"),\n' +
-                '       product, component (new tag), env, and the existing bucket identifier (e.g. bucketName).\n' +
-                '       Example: {"cloud":"gcp-conn","service":"gcs","type":"storage","product":"my-product",\n' +
-                '       "component":"assets","env":"snd","bucketName":"my-existing-bucket"}.\n' +
-                '       If import-persist fails, the error message now reports both the create failure and the\n' +
-                '       update fallback failure — read both to diagnose. Do not retry blindly.\n' +
-                '    3. Provision a brand-new bucket AND register it (see provision-persist docs below).\n' +
+                '    2. Import existing cloud buckets via cloud connections (no provisioning):\n' +
+                '         cloud resources import-persist-all -f import-all.json --json\n' +
+                '       File is a JSON ARRAY — one entry per env, all with the same product and component tag.\n' +
+                '       Each entry: cloud (connection tag), service (e.g. "gcs","s3"), type ("storage"),\n' +
+                '       product, component (new tag), env, resource (bucket name/identifier).\n' +
+                '       Example (two envs): [{"cloud":"gcp-snd","service":"gcs","type":"storage",\n' +
+                '       "product":"my-product","component":"assets","env":"snd","resource":"snd-bucket"},\n' +
+                '       {"cloud":"gcp-prd","service":"gcs","type":"storage","product":"my-product",\n' +
+                '       "component":"assets","env":"prd","resource":"prd-bucket"}].\n' +
+                '       All envs are imported in parallel, drafts merged, then the asset is created once.\n' +
+                '       Use import-persist (single-env form) only when the product has exactly one environment.\n' +
+                '       If import-persist-all fails, the error reports all create/update failures — do not retry blindly.\n' +
+                '    3. Provision brand-new buckets AND register them (see provision-persist-all docs below).\n' +
                 '  - Managing cloud connections and cloud-linked resources\n' +
                 '  - Discovering cloud tiers: "cloud tiers --provider <provider> --type <database|storage> [--db-type <type>] --json"\n' +
                 '    IMPORTANT: `cloud tiers` has no `list` verb. Use only a tier returned for the selected provider/type.\n' +
-                '  - Provisioning and persisting a cloud resource: "cloud resources provision-persist -f file.json --tier <tier_name> --json"\n' +
-                '    The JSON file requires: cloud (connection tag), service (provider service), type (Ductape component type),\n' +
-                '    product (product tag), component (new component tag), and env (existing environment slug).\n' +
-                '    Provider parameters such as region, location, bucketName, dbName, and waitForReady may be supplied in the file.\n' +
-                '    Example GCS Standard file: {"cloud":"gcp-tag","service":"gcs","type":"storage",' +
-                '"product":"product-tag","component":"assets","env":"snd","location":"us-central1"}.\n' +
-                '    Use `provision-persist` when the result must be registered as a Ductape asset; `provision` alone only returns\n' +
-                '    the provider resource and component draft. Tier discovery does not by itself prove that a connection supports\n' +
-                '    provisioning that service: if provisioning reports an unsupported provider/service pair, stop and report it.\n' +
+                '  - Provisioning and persisting cloud resources:\n' +
+                '    For a product with multiple environments always use provision-persist-all (not provision-persist):\n' +
+                '      cloud resources provision-persist-all -f file.json --json\n' +
+                '    File is a JSON ARRAY — one entry per env, all with the same product and component tag.\n' +
+                '    Each entry requires: cloud (connection tag), service (provider service), type (Ductape component type),\n' +
+                '    product (product tag), component (new component tag), env (existing environment slug).\n' +
+                '    Provider parameters such as region, location, bucketName, dbName, tier, and waitForReady\n' +
+                '    may be supplied per entry in the file.\n' +
+                '    Example (two envs): [{"cloud":"gcp-snd","service":"gcs","type":"storage",\n' +
+                '    "product":"product-tag","component":"assets","env":"snd","location":"us-central1"},\n' +
+                '    {"cloud":"gcp-prd","service":"gcs","type":"storage","product":"product-tag",\n' +
+                '    "component":"assets","env":"prd","location":"us-central1"}].\n' +
+                '    Use provision-persist (single-env) only when the product has exactly one environment.\n' +
+                '    Use provision alone when you only need the provider resource without registering an asset.\n' +
+                '    Tier discovery does not by itself prove that a connection supports provisioning that service:\n' +
+                '    if provisioning reports an unsupported provider/service pair, stop and report it.\n' +
                 '    Never infer an environment, provider service, region, tier, or cost. List/verify each before provisioning.\n' +
                 '  - Known provisioning limitations: MongoDB Atlas (M0 free tier) and Neo4j Aura cannot be provisioned via\n' +
                 '    Ductape — they are import-only. Only AWS, GCP, and Azure managed services support provision-persist.\n' +

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ductape/mcp",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",

package/src/index.ts

@@ -79,10 +79,11 @@ There are THREE categories of operations. Use the right tool for each:
        ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
        messageBroker, graph, vector, and any other resource with an envs array):
        The envs array MUST contain one entry for EVERY environment defined on the product.
-       import-persist and provision-persist enforce this with a preflight check: if the
-       generated draft does not cover all product environments the operation fails immediately
-       with error code MISSING_ENV_COVERAGE and a message listing exactly which envs are absent.
-       No creation or mutation is attempted. You cannot scope an asset to a subset of environments.
+       import-persist and provision-persist only generate a draft for ONE env at a time.
+       Calling import-persist once will fail with MISSING_ENV_COVERAGE because the single-env
+       draft does not cover all product environments. Use import-persist-all or
+       provision-persist-all instead — they accept an array of per-env inputs, import/provision
+       each env in parallel, merge the drafts, and persist once with full env coverage.
 
        BEFORE constructing any resource file or initiating import/provision:
          1. Run: ductape_cli("products environments list <product_tag> --json")
@@ -90,6 +91,16 @@ There are THREE categories of operations. Use the right tool for each:
          3. Collect connection details or confirmation for EACH slug from the user.
             Do not proceed until you have details for every env.
 
+       Use import-persist-all / provision-persist-all (not the single-env forms) whenever
+       you have details for all envs. The file must be a JSON array — one object per env,
+       same format as a single import-persist/provision-persist input, all sharing the same
+       product and component tag. Example:
+         [{"cloud":"gcp-snd","service":"gcs","type":"storage","product":"my-prod",
+           "component":"assets","env":"snd","resource":"snd-bucket"},
+          {"cloud":"gcp-prd","service":"gcs","type":"storage","product":"my-prod",
+           "component":"assets","env":"prd","resource":"prd-bucket"}]
+         → ductape_cli("cloud resources import-persist-all -f all-envs.json --json")
+
        Sharing one resource across multiple envs is allowed but must be confirmed per env:
          - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
          - Never assume shared configuration without confirmation.
@@ -1257,27 +1268,38 @@ async function main() {
           '         resources storage create -f storage.json\n' +
           '       File shape: { name, tag, envs: [{ slug, type: "aws"|"gcp"|"azure", config: { bucketName, ...creds } }] }\n' +
           '       For cloud-linked envs set config.cloud to the connection tag and omit raw credentials.\n' +
-          '    2. Import an existing cloud bucket via a cloud connection (no provisioning):\n' +
-          '         cloud resources import-persist -f import.json --json\n' +
-          '       File requires: cloud (connection tag), service (e.g. "gcs","s3"), type ("storage"),\n' +
-          '       product, component (new tag), env, and the existing bucket identifier (e.g. bucketName).\n' +
-          '       Example: {"cloud":"gcp-conn","service":"gcs","type":"storage","product":"my-product",\n' +
-          '       "component":"assets","env":"snd","bucketName":"my-existing-bucket"}.\n' +
-          '       If import-persist fails, the error message now reports both the create failure and the\n' +
-          '       update fallback failure — read both to diagnose. Do not retry blindly.\n' +
-          '    3. Provision a brand-new bucket AND register it (see provision-persist docs below).\n' +
+          '    2. Import existing cloud buckets via cloud connections (no provisioning):\n' +
+          '         cloud resources import-persist-all -f import-all.json --json\n' +
+          '       File is a JSON ARRAY — one entry per env, all with the same product and component tag.\n' +
+          '       Each entry: cloud (connection tag), service (e.g. "gcs","s3"), type ("storage"),\n' +
+          '       product, component (new tag), env, resource (bucket name/identifier).\n' +
+          '       Example (two envs): [{"cloud":"gcp-snd","service":"gcs","type":"storage",\n' +
+          '       "product":"my-product","component":"assets","env":"snd","resource":"snd-bucket"},\n' +
+          '       {"cloud":"gcp-prd","service":"gcs","type":"storage","product":"my-product",\n' +
+          '       "component":"assets","env":"prd","resource":"prd-bucket"}].\n' +
+          '       All envs are imported in parallel, drafts merged, then the asset is created once.\n' +
+          '       Use import-persist (single-env form) only when the product has exactly one environment.\n' +
+          '       If import-persist-all fails, the error reports all create/update failures — do not retry blindly.\n' +
+          '    3. Provision brand-new buckets AND register them (see provision-persist-all docs below).\n' +
           '  - Managing cloud connections and cloud-linked resources\n' +
           '  - Discovering cloud tiers: "cloud tiers --provider <provider> --type <database|storage> [--db-type <type>] --json"\n' +
           '    IMPORTANT: `cloud tiers` has no `list` verb. Use only a tier returned for the selected provider/type.\n' +
-          '  - Provisioning and persisting a cloud resource: "cloud resources provision-persist -f file.json --tier <tier_name> --json"\n' +
-          '    The JSON file requires: cloud (connection tag), service (provider service), type (Ductape component type),\n' +
-          '    product (product tag), component (new component tag), and env (existing environment slug).\n' +
-          '    Provider parameters such as region, location, bucketName, dbName, and waitForReady may be supplied in the file.\n' +
-          '    Example GCS Standard file: {"cloud":"gcp-tag","service":"gcs","type":"storage",' +
-          '"product":"product-tag","component":"assets","env":"snd","location":"us-central1"}.\n' +
-          '    Use `provision-persist` when the result must be registered as a Ductape asset; `provision` alone only returns\n' +
-          '    the provider resource and component draft. Tier discovery does not by itself prove that a connection supports\n' +
-          '    provisioning that service: if provisioning reports an unsupported provider/service pair, stop and report it.\n' +
+          '  - Provisioning and persisting cloud resources:\n' +
+          '    For a product with multiple environments always use provision-persist-all (not provision-persist):\n' +
+          '      cloud resources provision-persist-all -f file.json --json\n' +
+          '    File is a JSON ARRAY — one entry per env, all with the same product and component tag.\n' +
+          '    Each entry requires: cloud (connection tag), service (provider service), type (Ductape component type),\n' +
+          '    product (product tag), component (new component tag), env (existing environment slug).\n' +
+          '    Provider parameters such as region, location, bucketName, dbName, tier, and waitForReady\n' +
+          '    may be supplied per entry in the file.\n' +
+          '    Example (two envs): [{"cloud":"gcp-snd","service":"gcs","type":"storage",\n' +
+          '    "product":"product-tag","component":"assets","env":"snd","location":"us-central1"},\n' +
+          '    {"cloud":"gcp-prd","service":"gcs","type":"storage","product":"product-tag",\n' +
+          '    "component":"assets","env":"prd","location":"us-central1"}].\n' +
+          '    Use provision-persist (single-env) only when the product has exactly one environment.\n' +
+          '    Use provision alone when you only need the provider resource without registering an asset.\n' +
+          '    Tier discovery does not by itself prove that a connection supports provisioning that service:\n' +
+          '    if provisioning reports an unsupported provider/service pair, stop and report it.\n' +
           '    Never infer an environment, provider service, region, tier, or cost. List/verify each before provisioning.\n' +
           '  - Known provisioning limitations: MongoDB Atlas (M0 free tier) and Neo4j Aura cannot be provisioned via\n' +
           '    Ductape — they are import-only. Only AWS, GCP, and Azure managed services support provision-persist.\n' +