postman-cli-completion 1.58.0 → 1.60.0

package/completions/zsh/_postman

@@ -1,6 +1,6 @@
 #compdef postman
 compdef _postman postman
-# Zsh completion for Postman CLI (postman v1.58.0)
+# Zsh completion for Postman CLI (postman v1.60.0)
 # Auto-generated by scripts/generate.mjs — DO NOT EDIT
 # Source: spec/commands.json
 # https://github.com/yokawasa/postman-cli-completion
@@ -25,6 +25,7 @@ _postman() {
         logout) _postman_logout ;;
         init) _postman_init ;;
         whoami) _postman_whoami ;;
+        update) _postman_update ;;
         skills) _postman_skills ;;
         collection) _postman_collection ;;
         environment) _postman_environment ;;
@@ -56,16 +57,17 @@ _postman_commands() {
   local -a commands
   commands=(
     'login:Authenticate with Postman to access your resources.'
-    'signup:Sign up to keep the work you created as a guest (claims your guest workspace). By default prints a single-use sign-up URL to open in a browser; --browser signs up in a browser and signs this CLI in.'
+    'signup:Sign up to keep the work you created as a guest (claims your guest workspace). Waits and signs this CLI in once the sign-up is completed in a browser — opening that browser here on a terminal, or printing the URL to hand over when output is piped.'
     'logout:Delete the stored Postman API key.'
     'init:Set up Postman artifacts and agent instructions in a repository.'
     'whoami:Show the Postman account or guest session this CLI session is using.'
+    'update:Update Postman CLI using the original installation method.'
     'skills:Check and update the agent skills in this repository.'
     'collection:Run and test your Postman collections directly from the command line.'
     'environment:Work with local Postman environments from the command line. Also read cloud environments by ID.'
     'globals:Work with local Postman globals from the command line.'
     'api:Publish and test your APIs directly from the command line'
-    'runner:Where your monitors execute\: run and inspect your own self-hosted runners, and list the Postman-operated regions available to your team'
+    'runner:Where your monitors execute\: run and inspect your own self-hosted runners, and list the Postman-operated regions available to your team.'
     'spec:Lint and validate Specifications from the command line'
     'monitor:Run and manage Postman monitors.'
     'workspace:Manage workspace resources.'
@@ -100,7 +102,7 @@ _postman_login() {
 
 _postman_signup() {
   _arguments \
-    '--browser[Open a browser to sign up and sign this CLI in, instead of printing a URL.]' \
+    '--guest[Start working as an anonymous guest instead of signing up — no account or browser needed, so it works anywhere. Your work is saved to a temporary workspace you can keep later by running `postman signup`.]' \
     '--json[Print the sign-up details as machine-readable JSON.]' \
     '(-h --help)'{-h,--help}'[display help for command]'
 }
@@ -130,6 +132,12 @@ _postman_whoami() {
     '(-h --help)'{-h,--help}'[display help for command]'
 }
 
+_postman_update() {
+  _arguments \
+    '--check[Check whether a Postman CLI update is available.]' \
+    '(-h --help)'{-h,--help}'[display help for command]'
+}
+
 _postman_skills() {
   local context state state_descr line
   typeset -A opt_args
@@ -183,9 +191,12 @@ _postman_collection() {
   case $state in
     args)
       case $words[1] in
+        new) _postman_collection_new ;;
         migrate) _postman_collection_migrate ;;
         lint) _postman_collection_lint ;;
         ai-readiness) _postman_collection_ai_readiness ;;
+        get) _postman_collection_get ;;
+        list) _postman_collection_list ;;
         run) _postman_collection_run ;;
       esac
       ;;
@@ -195,14 +206,27 @@ _postman_collection() {
 _postman_collection_commands() {
   local -a sub
   sub=(
+    'new:Scaffold a v3 collection on disk, or create one in a cloud Postman workspace with --workspace.'
     'migrate:Migrate a v2.1 collection to the v3 format'
     'lint:Run linting on a local v3 collection at the given file or directory path.'
     'ai-readiness:Score a Postman collection for AI readiness by ID, local file path, or local-mode directory.'
+    'get:Fetch a Postman collection in the V3 format and print it.'
+    'list:List collections\: your local project'\''s collections by default, or a Postman cloud workspace'\''s collections with --workspace.'
     'run:Initiate a Postman collection run from a given ID or path.'
   )
   _describe -t commands 'collection command' sub
 }
 
+_postman_collection_new() {
+  _arguments \
+    '(-w --workspace)'{-w,--workspace}'[Create the collection in a cloud Postman workspace instead of scaffolding it locally. Required when the current directory is not a local Postman workspace.]:workspaceId' \
+    '--force[Rewrite the definition of an existing local collection. Existing request files are left alone.]' \
+    '--verbose[Verbose output]' \
+    '--json[JSON output]' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:name:'
+}
+
 _postman_collection_migrate() {
   _arguments \
     '(-o --output)'{-o,--output}'[Output directory (default\: ./<collection-name>)]:dir:_files -g "*.json"' \
@@ -226,6 +250,24 @@ _postman_collection_ai_readiness() {
     '*:collectionId/Path:_files -g "*.json"'
 }
 
+_postman_collection_get() {
+  _arguments \
+    '--api-key[Postman API key (defaults to your `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--json[Print the collection as machine-readable V3 JSON instead of a table]' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:id:'
+}
+
+_postman_collection_list() {
+  _arguments \
+    '(-w --workspace)'{-w,--workspace}'[List a Postman cloud workspace'\''s collections by id. Omit to list the local project'\''s collections.]:workspaceId' \
+    '(-f --filter)'{-f,--filter}'[Filter collections by name.]:name' \
+    '--verbose[Verbose output]' \
+    '--debug[Debug output]' \
+    '--json[JSON output]' \
+    '(-h --help)'{-h,--help}'[display help for command]'
+}
+
 _postman_collection_run() {
   _arguments \
     '(-e --environment)'{-e,--environment}'[Specify an Id or path to a Postman Environment]:path:_files -g "*.json"' \
@@ -295,6 +337,7 @@ _postman_environment() {
   case $state in
     args)
       case $words[1] in
+        new) _postman_environment_new ;;
         list) _postman_environment_list ;;
         get) _postman_environment_get ;;
         var) _postman_environment_var ;;
@@ -307,6 +350,7 @@ _postman_environment() {
 _postman_environment_commands() {
   local -a sub
   sub=(
+    'new:Scaffold a local environment file, or create one in a Postman workspace with --workspace.'
     'list:List environments in a Postman workspace.'
     'get:Read an environment by ID or local environment file path.'
     'var:Read and update environment variables.'
@@ -315,6 +359,16 @@ _postman_environment_commands() {
   _describe -t commands 'environment command' sub
 }
 
+_postman_environment_new() {
+  _arguments \
+    '(-w --workspace)'{-w,--workspace}'[Create the environment in a cloud Postman workspace instead of scaffolding it locally. Required when the current directory is not a local Postman workspace.]:workspaceId' \
+    '--force[Overwrite an existing local environment file.]' \
+    '--verbose[Verbose output]' \
+    '--json[JSON output]' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:name:'
+}
+
 _postman_environment_list() {
   _arguments \
     '(-w --workspace)'{-w,--workspace}'[Workspace ID to list environments from.]:workspaceId' \
@@ -498,9 +552,9 @@ _postman_runner() {
 _postman_runner_commands() {
   local -a sub
   sub=(
-    'start:Start a runner'
-    'list:List the team'\''s registered self-hosted runners'
-    'regions:List the region and private-runner values valid for monitor create/update --runner, including a static IP where configured'
+    'start:Start a self-hosted runner in your own network.'
+    'list:List the team'\''s registered self-hosted runners.'
+    'regions:List the region and private-runner values valid for monitor create/update --runner, with the static IP Postman runs each one from, where your team has access to it.'
   )
   _describe -t commands 'runner command' sub
 }
@@ -509,21 +563,23 @@ _postman_runner_start() {
   _arguments \
     '--id[The ID of the runner to execute]:id' \
     '--key[The secret key for the runner]:key:_files -g "*.(pem|crt|key)"' \
-    '--region[Specify the region for the runner. Use "eu" for EU region.]:region' \
-    '--proxy[External proxy URL (e.g., http\://proxy.com or http\://proxy.com\:8080)]:url' \
+    '--region[Region this runner reports to -- use "eu" for the EU region]:region' \
+    '--proxy[External proxy URL, for example http\://proxy.com or http\://proxy.com\:8080]:url' \
     '--egress-proxy[Enable built-in egress proxy]' \
     '--egress-proxy-authz-url[Custom egress proxy authorization service base URL]:url' \
     '--ssl-extra-ca-certs[Additional trusted CA certificates (PEM file, can contain multiple certs)]:path:_files -g "*.(pem|crt|key)"' \
+    '--dataset-jdbc-driver-dir[Folder on this machine holding the JDBC driver .jar files you put there. Required to run a dataset that uses a JDBC source. Drivers are loaded only from this folder and matched by file name; driver paths saved in the dataset are ignored]:path:_files -/' \
     '--metrics[Enable the metrics server for health checks]' \
     '--metrics-port[Port for the metrics server (default\: "9090")]:port' \
-    '--report-events[Accepted for compatibility; analytics are sent by default]' \
-    '--no-report-events[Do not send analytics to Postman]' \
+    '--report-events[Accepted for compatibility; run events are reported by default]' \
+    '--no-report-events[Do not report run events to Postman]' \
     '(-h --help)'{-h,--help}'[display help for command]'
 }
 
 _postman_runner_list() {
   _arguments \
     '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '(-w --workspace)'{-w,--workspace}'[Filter to runners in this workspace]:id' \
     '--json[Output the runner list as JSON instead of a table]' \
     '(-h --help)'{-h,--help}'[display help for command]'
 }
@@ -551,6 +607,7 @@ _postman_spec() {
         get) _postman_spec_get ;;
         file) _postman_spec_file ;;
         create) _postman_spec_create ;;
+        generate) _postman_spec_generate ;;
       esac
       ;;
   esac
@@ -565,6 +622,7 @@ _postman_spec_commands() {
     'get:Read a spec definition, including every file of a multi-file spec.'
     'file:Add, update, or remove files in a spec (cloud ID or local directory).'
     'create:Create a new spec in a workspace, or (with path) scaffold a local spec file.'
+    'generate:Generate artifacts from a specification.'
   )
   _describe -t commands 'spec command' sub
 }
@@ -670,6 +728,40 @@ _postman_spec_create() {
     '*:path:_files -g "*.json"'
 }
 
+_postman_spec_generate() {
+  local context state state_descr line
+  typeset -A opt_args
+  _arguments -C \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '1: :_postman_spec_generate_commands' \
+    '*::arg:->args'
+  case $state in
+    args)
+      case $words[1] in
+        collection) _postman_spec_generate_collection ;;
+      esac
+      ;;
+  esac
+}
+
+_postman_spec_generate_commands() {
+  local -a sub
+  sub=(
+    'collection:Generate a Postman collection from a specification.'
+  )
+  _describe -t commands 'generate command' sub
+}
+
+_postman_spec_generate_collection() {
+  _arguments \
+    '(-n --name)'{-n,--name}'[Collection name]:name' \
+    '--folder-strategy[Folder strategy\: Paths or Tags (default\: Paths) (default\: "Paths")]:strategy' \
+    '(-w --workspace)'{-w,--workspace}'[Workspace ID (cloud mode)]:id' \
+    '--api-key[Postman API key]:key:_files -g "*.(pem|crt|key)"' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:spec:'
+}
+
 _postman_monitor() {
   local context state state_descr line
   typeset -A opt_args
@@ -688,6 +780,7 @@ _postman_monitor() {
         runs) _postman_monitor_runs ;;
         list) _postman_monitor_list ;;
         get) _postman_monitor_get ;;
+        metrics) _postman_monitor_metrics ;;
         pause) _postman_monitor_pause ;;
         resume) _postman_monitor_resume ;;
       esac
@@ -706,6 +799,7 @@ _postman_monitor_commands() {
     'runs:Inspect a monitor run'\''s attempts.'
     'list:List the monitors visible to you.'
     'get:Show a monitor'\''s configuration.'
+    'metrics:Show per-request latency and outcome history for a monitor.'
     'pause:Pause a monitor, so it stops firing on schedule.'
     'resume:Resume a paused monitor, so it fires on schedule again.'
   )
@@ -714,7 +808,7 @@ _postman_monitor_commands() {
 
 _postman_monitor_run() {
   _arguments \
-    '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
     '(-x --suppress-exit-code)'{-x,--suppress-exit-code}'[Specify whether or not to override the default exit code for the current run]' \
     '(-t --timeout)'{-t,--timeout}'[Maximum wait time for run completion in milliseconds (default\: 15 minutes) (default\: 900000)]:ms' \
     '--async[Submit the run and return immediately with its job id and Postman URL, without waiting for completion]' \
@@ -727,14 +821,14 @@ _postman_monitor_create() {
   _arguments \
     '(-c --collection)'{-c,--collection}'[Collection to monitor -- accepts the id shown in the Postman app, prefixed or bare]:id' \
     '--name[Monitor name (defaults to the linked collection'\''s own name)]:name' \
-    '--environment[Environment to run the monitored collection with]:id' \
+    '(-e --environment)'{-e,--environment}'[Environment to run the monitored collection with]:id' \
     '(-w --workspace)'{-w,--workspace}'[Workspace to create the monitor in (defaults to the workspace named in the local .postman/resources.yaml manifest; required if neither is available)]:id' \
     '--schedule[Cron expression for the monitor'\''s schedule]:cron' \
-    '--timezone[Time zone for --schedule, e.g. America/New_York (defaults to the host machine'\''s own zone)]:tz' \
+    '--timezone[Time zone for --schedule, for example America/New_York (defaults to the host machine'\''s own zone)]:tz' \
     '--runner[A Postman region name (see `postman runner regions`) or the id of a self-hosted runner created in Postman (list existing ones with `postman runner list`) to run from (repeatable) (default\: \[\])]:value' \
     '--notify-email[Email to notify on a run failure or error (repeatable) (default\: \[\])]:email' \
-    '--notification-limit[Cap consecutive notifications before they are muted (service range\: 1-99)]:n' \
-    '--retry[Retries on a failed run (service caps this at 2)]:n' \
+    '--notification-limit[Consecutive failure notifications to send before muting them]:n' \
+    '--retry[Times to retry a failed run]:n' \
     '--timeout[Request timeout in milliseconds]:ms' \
     '--delay[Delay between requests in milliseconds]:ms' \
     '--strict-ssl[Fail the run when the target'\''s TLS certificate cannot be verified]' \
@@ -744,7 +838,7 @@ _postman_monitor_create() {
     '--dataset-id[Dataset to use as iteration data (used together with --dataset-view-id)]:id' \
     '--dataset-view-id[Dataset view to iterate (used together with --dataset-id)]:id' \
     '--iteration-count[Number of iterations to run]:n' \
-    '--iteration-strategy[How iteration data is consumed, e.g. round_robin, repeat_last, stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)]:strategy' \
+    '--iteration-strategy[How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)]:strategy' \
     '--no-run-now[Do not trigger an immediate run after creating the monitor]' \
     '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
     '--json[Output as JSON instead of a table]' \
@@ -755,12 +849,14 @@ _postman_monitor_update() {
   _arguments \
     '--name[New monitor name]:name' \
     '--schedule[New cron expression for the monitor'\''s schedule]:cron' \
-    '--timezone[Time zone for --schedule, e.g. America/New_York (defaults to the host machine'\''s own zone)]:tz' \
+    '--timezone[Time zone for --schedule, for example America/New_York (defaults to the host machine'\''s own zone)]:tz' \
     '--runner[A Postman region name (see `postman runner regions`) or the id of a self-hosted runner created in Postman (list existing ones with `postman runner list`) to run from (repeatable; replaces the current set) (default\: \[\])]:value' \
     '--notify-email[Email to notify on a run failure or error (repeatable; replaces the current list) (default\: \[\])]:email' \
     '--clear-notifications[Remove every notification recipient]' \
-    '--notification-limit[Cap consecutive notifications before they are muted (service range\: 1-99)]:n' \
-    '--retry[Retries on a failed run (service caps this at 2)]:n' \
+    '(-e --environment)'{-e,--environment}'[Environment to run the monitored collection with (replaces the current one)]:id' \
+    '--clear-environment[Run the monitored collection with no environment]' \
+    '--notification-limit[Consecutive failure notifications to send before muting them]:n' \
+    '--retry[Times to retry a failed run]:n' \
     '--timeout[Request timeout in milliseconds]:ms' \
     '--delay[Delay between requests in milliseconds]:ms' \
     '--strict-ssl[Fail the run when the target'\''s TLS certificate cannot be verified]' \
@@ -770,7 +866,7 @@ _postman_monitor_update() {
     '--dataset-id[Dataset to use as iteration data (used together with --dataset-view-id)]:id' \
     '--dataset-view-id[Dataset view to iterate (used together with --dataset-id)]:id' \
     '--iteration-count[Number of iterations to run]:n' \
-    '--iteration-strategy[How iteration data is consumed, e.g. round_robin, repeat_last, stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)]:strategy' \
+    '--iteration-strategy[How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)]:strategy' \
     '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
     '--json[Output as JSON instead of a table]' \
     '(-h --help)'{-h,--help}'[display help for command]' \
@@ -814,9 +910,9 @@ _postman_monitor_jobs_commands() {
 
 _postman_monitor_jobs_list() {
   _arguments \
-    '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
-    '--result[Filter by outcome, e.g. success, failure, error, abort (server-validated, not a fixed list)]:value' \
-    '--trigger[Filter by trigger, e.g. api, schedule, webhook, postman-cli (server-validated, not a fixed list)]:value' \
+    '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--result[Filter by outcome, for example success, failure, error or abort]:value' \
+    '--trigger[Filter by trigger, for example api, schedule, webhook or postman-cli]:value' \
     '--since[Only jobs that finished at or after this ISO 8601 date-time]:dateTime' \
     '--limit[Maximum number of jobs to return]:n' \
     '--cursor[Opaque pagination cursor]:token' \
@@ -827,7 +923,7 @@ _postman_monitor_jobs_list() {
 
 _postman_monitor_jobs_get() {
   _arguments \
-    '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
     '--json[Output as JSON instead of a table]' \
     '(-h --help)'{-h,--help}'[display help for command]' \
     '*:jobId:'
@@ -859,8 +955,8 @@ _postman_monitor_runs_commands() {
 
 _postman_monitor_runs_get() {
   _arguments \
-    '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
-    '--attempt[Which attempt of the run to show, counting from 0 (default\: the latest)]:n' \
+    '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--attempt[Which attempt of the run to show, where 0 is the first (default\: the most recent)]:n' \
     '--failed-only[Show only failed assertions]' \
     '--json[Output as JSON instead of a table]' \
     '(-h --help)'{-h,--help}'[display help for command]' \
@@ -872,15 +968,14 @@ _postman_monitor_list() {
     '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
     '(-w --workspace)'{-w,--workspace}'[Filter to monitors in this workspace]:id' \
     '(-c --collection)'{-c,--collection}'[Filter to monitors on this collection]:id' \
-    '--environment[Filter to monitors on this environment]:id' \
-    '--runner[Filter to a Self-Hosted Runner ID (not a Postman Region). Cannot be combined with --workspace, --collection, --environment, --owner, --team or --active.]:id' \
+    '(-e --environment)'{-e,--environment}'[Filter to monitors on this environment]:id' \
+    '--runner[Filter to a self-hosted runner id, not a Postman region. Cannot be combined with --workspace, --collection, --environment, --owner, --team or --active]:id' \
     '--owner[Filter to monitors created by this user id (shown in the Owner column)]:id' \
     '--team[Filter to monitors owned by your own team]' \
     '--active[Filter by active state]:true|false' \
-    '--limit[Max monitors to return. The service caps page size and rejects a value above it with its own error.]:n' \
-    '--offset[Not supported\: the service accepts this parameter and silently ignores it. Refused locally. Use --cursor instead.]:n' \
-    '--cursor[Pagination cursor from a previous page'\''s response.]:token' \
-    '--columns[Comma-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available\: State, Notifications, Environment, Runners.]:names' \
+    '--limit[Maximum number of monitors to return (Postman caps the page size and rejects a larger value)]:n' \
+    '--cursor[Pagination cursor from a previous page'\''s response]:token' \
+    '--columns[Comma-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available\: State, Notifications, Environment, Runners]:names' \
     '--no-headers[Omit the header row]' \
     '(-f --filter)'{-f,--filter}'[Show only monitors whose name contains this text (applies to the returned page, case-insensitive)]:text' \
     '--sort[Sort the returned page by "name" or "active"]:field' \
@@ -896,6 +991,18 @@ _postman_monitor_get() {
     '*:monitorId:'
 }
 
+_postman_monitor_metrics() {
+  _arguments \
+    '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--since[Only executions at or after this ISO 8601 date-time (defaults to 7 days ago)]:dateTime' \
+    '--until[Only executions at or before this ISO 8601 date-time (defaults to now)]:dateTime' \
+    '(-f --filter)'{-f,--filter}'[Show only requests whose name contains this text (case-insensitive)]:text' \
+    '--limit[Maximum number of rows to show\: executions, newest first, under --json, or requests, worst-behaving first, in the table. Applied to the results after they are fetched, so it does not make the command faster]:n' \
+    '--json[Output as JSON instead of a table]' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:monitorId:'
+}
+
 _postman_monitor_pause() {
   _arguments \
     '--api-key[Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
@@ -926,9 +1033,11 @@ _postman_workspace() {
         prepare) _postman_workspace_prepare ;;
         push) _postman_workspace_push ;;
         lint) _postman_workspace_lint ;;
+        get) _postman_workspace_get ;;
         create) _postman_workspace_create ;;
         pull) _postman_workspace_pull ;;
         connect-git) _postman_workspace_connect_git ;;
+        diff) _postman_workspace_diff ;;
       esac
       ;;
   esac
@@ -941,9 +1050,11 @@ _postman_workspace_commands() {
     'prepare:Prepare local collections and environments for push by validating and regenerating IDs if needed.'
     'push:Push local workspace entities (collections, environments, specifications, mocks and more) to Postman workspace.'
     'lint:Lint the current local Postman workspace\: its configuration (.postman/resources.yaml) plus every discovered entity. Use --meta to lint only the configuration.'
+    'get:Read a workspace'\''s metadata, and optionally the ids of what it holds.'
     'create:Create a Postman workspace and bind it to this git repository.'
     'pull:Pull workspace entities from a Postman workspace into the local git-native folder.'
     'connect-git:Connect a Postman workspace to a local git repository.'
+    'diff:Preview local-vs-cloud drift before pushing. Read-only\: nothing is created, updated or deleted.'
   )
   _describe -t commands 'workspace command' sub
 }
@@ -985,6 +1096,15 @@ _postman_workspace_lint() {
     '(-h --help)'{-h,--help}'[display help for command]'
 }
 
+_postman_workspace_get() {
+  _arguments \
+    '--elements[Also report the resources the workspace holds.]' \
+    '--json[Print the workspace as machine-readable JSON.]' \
+    '--timeout[Milliseconds to wait for the API (default 30000).]:ms' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:id:'
+}
+
 _postman_workspace_create() {
   _arguments \
     '--visibility[Required. Workspace visibility, e.g. personal or team]:status' \
@@ -1012,6 +1132,18 @@ _postman_workspace_connect_git() {
     '*:path:_files -g "*.json"'
 }
 
+_postman_workspace_diff() {
+  _arguments \
+    '--push-strategy[Strategy to preview. "force-sync" also shows cloud entities that would be DELETED. Defaults to "force-sync".]:strategy' \
+    '--summary[Skip content comparison. Faster, but updates are listed without checking whether they changed.]' \
+    '--json[Print the diff as machine-readable JSON.]' \
+    '--exit-code[Exit with code 1 when drift is found (for CI gates).]' \
+    '--verbose[Show detailed logging]' \
+    '--timeout[Abort the run after this many milliseconds. Defaults to 120000.]:ms' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:workspaceId:'
+}
+
 _postman_performance() {
   local context state state_descr line
   typeset -A opt_args
@@ -1023,6 +1155,7 @@ _postman_performance() {
     args)
       case $words[1] in
         run) _postman_performance_run ;;
+        list) _postman_performance_list ;;
       esac
       ;;
   esac
@@ -1032,6 +1165,7 @@ _postman_performance_commands() {
   local -a sub
   sub=(
     'run:Run a performance test on a collection'
+    'list:List past performance runs for a collection, newest first.'
   )
   _describe -t commands 'performance command' sub
 }
@@ -1057,6 +1191,16 @@ _postman_performance_run() {
     '*:collectionId:_files -g "*.json"'
 }
 
+_postman_performance_list() {
+  _arguments \
+    '(-c --collection-id)'{-c,--collection-id}'[Collection ID whose performance runs to list]:id' \
+    '--cursor[Pagination cursor from a previous page'\''s response]:token' \
+    '--json[Output as JSON instead of a table]' \
+    '--timeout[Milliseconds to wait for the service before failing (default\: "30000")]:ms' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:id:'
+}
+
 _postman_flows() {
   local context state state_descr line
   typeset -A opt_args
@@ -1428,7 +1572,7 @@ _postman_mock_commands() {
     'push:Upload a mock from your repository to Postman cloud (creates it the first time, updates it after).'
     'deploy:Turn a mock in Postman cloud into a live mock server others can call over the internet.'
     'get:Show a mock'\''s details using its path if it lives in your repository, or its id if it lives in Postman cloud.'
-    'list:List the mocks in your Postman cloud workspace, or — with a folder path — the mocks in that folder in your repository.'
+    'list:List the mocks in your repository or Postman cloud workspace'
     'log:Show the requests a live mock server has received and the responses it sent, using its id.'
     'delete:Delete a mock using its path if it lives in your repository, or its id if it lives in Postman cloud. Cannot be undone.'
   )
@@ -2184,6 +2328,7 @@ _postman_dataset() {
         delete) _postman_dataset_delete ;;
         source) _postman_dataset_source ;;
         view) _postman_dataset_view ;;
+        jdbc) _postman_dataset_jdbc ;;
       esac
       ;;
   esac
@@ -2199,6 +2344,7 @@ _postman_dataset_commands() {
     'delete:Permanently remove a dataset\: a local .dataset.yaml or a cloud dataset id.'
     'source:Inspect and manage a dataset'\''s datasources.'
     'view:Inspect and manage saved views on a dataset.'
+    'jdbc:Inspect JDBC drivers before attaching one to a dataset.'
   )
   _describe -t commands 'dataset command' sub
 }
@@ -2268,6 +2414,7 @@ _postman_dataset_source() {
         add) _postman_dataset_source_add ;;
         remove) _postman_dataset_source_remove ;;
         update) _postman_dataset_source_update ;;
+        test) _postman_dataset_source_test ;;
       esac
       ;;
   esac
@@ -2280,6 +2427,7 @@ _postman_dataset_source_commands() {
     'add:Add a datasource to a dataset.'
     'remove:Remove a datasource from a dataset (local YAML path or cloud id).'
     'update:Update fields on an existing datasource. Only the flags you provide are changed.'
+    'test:Open and close a real connection using a source'\''s stored configuration.'
   )
   _describe -t commands 'source command' sub
 }
@@ -2298,15 +2446,28 @@ _postman_dataset_source_add() {
     '(-n --name)'{-n,--name}'[Logical name for the source (becomes the SQL table name)]:name' \
     '--source-id[Override the generated source id (local dataset only)]:uuid' \
     '--format[Use this format instead of extension/type inference; file contents are not sniffed]:csv|json|mysql|postgres|sqlserver' \
-    '--type[Source kind; local is inferred when --file is provided]:local|mysql|postgresql|sqlserver' \
+    '--type[Source kind; local is inferred from --file, jdbc from --driver-jar]:local|mysql|postgresql|sqlserver|jdbc' \
     '--file[Path to a local CSV/JSON file (absolute or cwd-relative)]:path:_files -g "*.json"' \
     '--ref-only[Reference the file in place; do NOT copy into data_dir (local dataset)]' \
     '--force[When copying, overwrite an existing file at the destination (local dataset)]' \
     '--upload[Cloud dataset only\: upload --file as a postmancloudfile source (runs via /exec). Without --upload, --file is registered as a local_filesystem csv/json source read by the local engine.]' \
+    '--driver-jar[JDBC driver JAR(s). Repeatable, or pass several after one flag]:path...:_files -g "*.json"' \
+    '--driver-class[Driver class. Auto-resolved when the JAR contains exactly one]:fqcn' \
+    '--driver-name[Label for this driver type (defaults to the JAR filename)]:label' \
+    '--url-template[JDBC URL with {{placeholders}}, e.g. jdbc\:postgresql\://{{host}}\:{{port}}/{{database}}]:template' \
+    '--var[Value for a {{placeholder}}. Repeatable. Use vault\:<vaultId>/<secretId> for a secret. WARNING\: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.]:name=value...' \
+    '--prop[Driver connection property. Repeatable. Same vault\: syntax as --var]:name=value...' \
+    '--vars-file[JSON object of --var values; "-" reads stdin. Supports {"$vaultId"\:..,"$secretId"\:..} objects, and keeps secrets out of argv entirely]:path:_files -g "*.json"' \
+    '--from-source[Reuse another source'\''s driver JAR, class and URL template]:name' \
+    '--java-path[Java runtime to use. Machine-local only - never written to the dataset. Also read from POSTMAN_JDBC_JAVA_PATH]:path:_files -g "*.json"' \
+    '--no-test[Skip the pre-write connection test. Note that resolving the driver class still starts a JVM — on a machine with no Java, pass --driver-class (or --from-source) too]' \
+    '--ssh-target-host-variable[Template variable holding the tunnelled host (inferred when omitted)]:name' \
+    '--ssh-target-port-variable[Template variable holding the tunnelled port (inferred when omitted)]:name' \
+    '--json[Emit the result as JSON instead of prose]' \
     '--host[DB host (mysql/postgresql/sqlserver)]:host' \
     '--port[DB port (defaults to 1433 for sqlserver)]:port' \
-    '--user[DB user (warning\: stored as plaintext in the YAML).]:user' \
-    '--password[DB password. WARNING\: passing it here exposes it in `ps` output and shell history, and it is stored as plaintext in the dataset YAML (local) or sent in the request body (cloud). Prefer a restricted DB user; secure input (prompt / stdin / env) is planned.]:password' \
+    '--user[DB user. WARNING\: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.]:user' \
+    '--password[DB password. WARNING\: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.]:password' \
     '--database[DB database name]:db' \
     '--table[DB table name (required for sqlserver)]:table' \
     '--ssh-host[SSH bastion host]:host' \
@@ -2344,10 +2505,22 @@ _postman_dataset_source_update() {
     '--file[Replace the source file (local dataset only; cloud file replacement is unsupported)]:path:_files -g "*.json"' \
     '--ref-only[With --file, reference in place instead of copying (local dataset only)]' \
     '--force[With --file, overwrite the copied destination (local dataset only)]' \
+    '--driver-jar[Replace the JDBC driver JAR(s)]:path...:_files -g "*.json"' \
+    '--driver-class[Replace the JDBC driver class]:fqcn' \
+    '--driver-name[Rename the JDBC driver type label]:label' \
+    '--url-template[Replace the JDBC URL template]:template' \
+    '--var[Set a JDBC template variable. Merges onto the existing values. Use vault\:<vaultId>/<secretId> for a secret. WARNING\: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.]:name=value...' \
+    '--prop[Set a JDBC connection property. Merges, same vault\: syntax]:name=value...' \
+    '--unset-var[Remove a JDBC template variable. Merging alone can never remove a key]:name...' \
+    '--unset-prop[Remove a JDBC connection property]:name...' \
+    '--vars-file[JSON object of --var values; "-" reads stdin]:path:_files -g "*.json"' \
+    '--ssh-target-host-variable[Template variable holding the tunnelled host (JDBC)]:name' \
+    '--ssh-target-port-variable[Template variable holding the tunnelled port (JDBC)]:name' \
+    '--java-path[Java runtime for JDBC operations. Machine-local only]:path:_files -g "*.json"' \
     '--host[Update DB host (mysql/postgresql/sqlserver)]:host' \
     '--port[Update DB port]:port' \
-    '--user[Update DB user (warning\: stored as plaintext in the YAML).]:user' \
-    '--password[Update DB password. WARNING\: passing it here exposes it in `ps` output and shell history, and it is stored as plaintext in the dataset YAML (local) or sent in the request body (cloud). Prefer a restricted DB user; secure input (prompt / stdin / env) is planned.]:password' \
+    '--user[Update DB user. WARNING\: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.]:user' \
+    '--password[Update DB password. WARNING\: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.]:password' \
     '--database[Update DB database name]:db' \
     '--table[Update DB table name]:table' \
     '--ssh-host[Update SSH bastion host]:host' \
@@ -2365,10 +2538,21 @@ _postman_dataset_source_update() {
     '--host-name-in-certificate[Update SQL Server certificate hostname override]:hostname' \
     '--tls-min-version[Update SQL Server minimum TLS version]:1.2|1.3' \
     '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--json[Emit the result as JSON instead of prose]' \
     '(-h --help)'{-h,--help}'[display help for command]' \
     '*:sourceNameOrId:'
 }
 
+_postman_dataset_source_test() {
+  _arguments \
+    '(-d --dataset)'{-d,--dataset}'[Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset id]:datasetPathOrId' \
+    '(-n --name)'{-n,--name}'[Source to test]:name' \
+    '--java-path[Java runtime to use for a JDBC source. Machine-local only; also read from POSTMAN_JDBC_JAVA_PATH]:path:_files -g "*.json"' \
+    '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
+    '--json[Emit the result as JSON instead of prose]' \
+    '(-h --help)'{-h,--help}'[display help for command]'
+}
+
 _postman_dataset_view() {
   local context state state_descr line
   typeset -A opt_args
@@ -2425,7 +2609,9 @@ _postman_dataset_view_create() {
     '(-d --dataset)'{-d,--dataset}'[Dataset to add the view to — a local .dataset.yaml path or a cloud dataset id]:datasetPathOrId' \
     '(-n --name)'{-n,--name}'[View name]:name' \
     '(-q --query)'{-q,--query}'[SQL query the view executes]:sql' \
+    '(-s --source)'{-s,--source}'[Bind the view to one datasource and run the query natively against it, instead of through the federated SQLite layer. Same reference `dataset query -s` takes]:nameOrIdOrSlug' \
     '--view-id[Override the generated view id (local only; cloud assigns its own)]:uuid' \
+    '--json[Emit the result as JSON instead of prose]' \
     '--api-key[Postman API key (defaults to the `postman login` session)]:key:_files -g "*.(pem|crt|key)"' \
     '(-h --help)'{-h,--help}'[display help for command]'
 }
@@ -2448,6 +2634,40 @@ _postman_dataset_view_update() {
     '*:viewNameOrId:'
 }
 
+_postman_dataset_jdbc() {
+  local context state state_descr line
+  typeset -A opt_args
+  _arguments -C \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '1: :_postman_dataset_jdbc_commands' \
+    '*::arg:->args'
+  case $state in
+    args)
+      case $words[1] in
+        inspect) _postman_dataset_jdbc_inspect ;;
+      esac
+      ;;
+  esac
+}
+
+_postman_dataset_jdbc_commands() {
+  local -a sub
+  sub=(
+    'inspect:Detect Java, list driver classes, suggest a URL template and read driver properties.'
+  )
+  _describe -t commands 'jdbc command' sub
+}
+
+_postman_dataset_jdbc_inspect() {
+  _arguments \
+    '--driver-class[Introspect this class instead of auto-selecting]:fqcn' \
+    '--url-template[Use this URL template instead of the one inferred from the JAR filename]:template' \
+    '--java-path[Java runtime to use. Machine-local only — never written to a dataset. Also read from POSTMAN_JDBC_JAVA_PATH.]:path:_files -g "*.json"' \
+    '--json[Emit the discovery result as JSON]' \
+    '(-h --help)'{-h,--help}'[display help for command]' \
+    '*:jar...:'
+}
+
 _postman_dependency() {
   local context state state_descr line
   typeset -A opt_args