postman-cli-completion 1.59.0 → 1.60.0

package/completions/bash/postman.bash

@@ -1,4 +1,4 @@
-# Bash completion for Postman CLI (postman v1.59.0)
+# Bash 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
@@ -91,7 +91,7 @@ _postman_login() {
 
 _postman_signup() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "--browser --wait --no-wait --json -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "--guest --json -h --help" -- "$cur") )
     return 0
   fi
 }
@@ -127,7 +127,7 @@ _postman_whoami() {
 
 _postman_update() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "-h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "--check -h --help" -- "$cur") )
     return 0
   fi
 }
@@ -499,7 +499,7 @@ _postman_runner() {
 
 _postman_runner_start() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "--id --key --region --proxy --egress-proxy --egress-proxy-authz-url --ssl-extra-ca-certs --metrics --metrics-port --report-events --no-report-events -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "--id --key --region --proxy --egress-proxy --egress-proxy-authz-url --ssl-extra-ca-certs --dataset-jdbc-driver-dir --metrics --metrics-port --report-events --no-report-events -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
@@ -509,6 +509,9 @@ _postman_runner_start() {
     --ssl-extra-ca-certs)
       _postman_filematch '!*.@(pem|crt|key)' "$cur"
       return 0 ;;
+    --dataset-jdbc-driver-dir)
+      COMPREPLY=( $(compgen -d -- "$cur") )
+      return 0 ;;
   esac
 }
 
@@ -731,7 +734,7 @@ _postman_monitor_run() {
 
 _postman_monitor_create() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "-c --collection --name --environment -w --workspace --schedule --timezone --runner --notify-email --notification-limit --retry --timeout --delay --strict-ssl --insecure --follow-redirects --block-redirects --dataset-id --dataset-view-id --iteration-count --iteration-strategy --no-run-now --api-key --json -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "-c --collection --name -e --environment -w --workspace --schedule --timezone --runner --notify-email --notification-limit --retry --timeout --delay --strict-ssl --insecure --follow-redirects --block-redirects --dataset-id --dataset-view-id --iteration-count --iteration-strategy --no-run-now --api-key --json -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
@@ -743,7 +746,7 @@ _postman_monitor_create() {
 
 _postman_monitor_update() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "--name --schedule --timezone --runner --notify-email --clear-notifications --notification-limit --retry --timeout --delay --strict-ssl --insecure --follow-redirects --block-redirects --dataset-id --dataset-view-id --iteration-count --iteration-strategy --api-key --json -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "--name --schedule --timezone --runner --notify-email --clear-notifications -e --environment --clear-environment --notification-limit --retry --timeout --delay --strict-ssl --insecure --follow-redirects --block-redirects --dataset-id --dataset-view-id --iteration-count --iteration-strategy --api-key --json -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
@@ -832,7 +835,7 @@ _postman_monitor_runs_get() {
 
 _postman_monitor_list() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "--api-key -w --workspace -c --collection --environment --runner --owner --team --active --limit --offset --cursor --columns --no-headers -f --filter --sort --json -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "--api-key -w --workspace -c --collection -e --environment --runner --owner --team --active --limit --cursor --columns --no-headers -f --filter --sort --json -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
@@ -895,7 +898,7 @@ _postman_workspace() {
     if [[ "$cur" == -* ]]; then
       COMPREPLY=( $(compgen -W "-h --help" -- "$cur") )
     else
-      COMPREPLY=( $(compgen -W "list prepare push lint create pull connect-git diff" -- "$cur") )
+      COMPREPLY=( $(compgen -W "list prepare push lint get create pull connect-git diff" -- "$cur") )
     fi
     return 0
   fi
@@ -904,6 +907,7 @@ _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 ;;
@@ -945,6 +949,15 @@ _postman_workspace_lint() {
   esac
 }
 
+_postman_workspace_get() {
+  if [[ "$cur" == -* ]]; then
+    COMPREPLY=( $(compgen -W "--elements --json --timeout -h --help" -- "$cur") )
+    return 0
+  fi
+  case "$prev" in
+  esac
+}
+
 _postman_workspace_create() {
   if [[ "$cur" == -* ]]; then
     COMPREPLY=( $(compgen -W "--visibility --name --summary --path --no-connect --force -h --help" -- "$cur") )
@@ -988,13 +1001,13 @@ _postman_performance() {
     if [[ "$cur" == -* ]]; then
       COMPREPLY=( $(compgen -W "-h --help" -- "$cur") )
     else
-      COMPREPLY=( $(compgen -W "run runs" -- "$cur") )
+      COMPREPLY=( $(compgen -W "run list" -- "$cur") )
     fi
     return 0
   fi
   case "$subcmd" in
     run) _postman_performance_run ;;
-    runs) _postman_performance_runs ;;
+    list) _postman_performance_list ;;
   esac
 }
 
@@ -1011,7 +1024,7 @@ _postman_performance_run() {
   _postman_filematch '!*.@(json)' "$cur"
 }
 
-_postman_performance_runs() {
+_postman_performance_list() {
   if [[ "$cur" == -* ]]; then
     COMPREPLY=( $(compgen -W "-c --collection-id --cursor --json --timeout -h --help" -- "$cur") )
     return 0
@@ -1961,7 +1974,7 @@ _postman_dataset() {
     if [[ "$cur" == -* ]]; then
       COMPREPLY=( $(compgen -W "-h --help" -- "$cur") )
     else
-      COMPREPLY=( $(compgen -W "list get query create delete source view" -- "$cur") )
+      COMPREPLY=( $(compgen -W "list get query create delete source view jdbc" -- "$cur") )
     fi
     return 0
   fi
@@ -1973,6 +1986,7 @@ _postman_dataset() {
     delete) _postman_dataset_delete ;;
     source) _postman_dataset_source ;;
     view) _postman_dataset_view ;;
+    jdbc) _postman_dataset_jdbc ;;
   esac
 }
 
@@ -2043,7 +2057,7 @@ _postman_dataset_source() {
     if [[ "$cur" == -* ]]; then
       COMPREPLY=( $(compgen -W "-h --help" -- "$cur") )
     else
-      COMPREPLY=( $(compgen -W "list add remove update" -- "$cur") )
+      COMPREPLY=( $(compgen -W "list add remove update test" -- "$cur") )
     fi
     return 0
   fi
@@ -2052,6 +2066,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
 }
 
@@ -2069,13 +2084,22 @@ _postman_dataset_source_list() {
 
 _postman_dataset_source_add() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "-d --dataset -n --name --source-id --format --type --file --ref-only --force --upload --host --port --user --password --database --table --ssh-host --ssh-port --ssh-user --ssh-private-key --ssh-host-key --ssh-host-key-vault-id --ssh-host-key-secret-id --ssh-insecure-skip-host-key-verification --schema --encrypt --trust-server-certificate --tls-certificate --host-name-in-certificate --tls-min-version --api-key -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "-d --dataset -n --name --source-id --format --type --file --ref-only --force --upload --driver-jar --driver-class --driver-name --url-template --var --prop --vars-file --from-source --java-path --no-test --ssh-target-host-variable --ssh-target-port-variable --json --host --port --user --password --database --table --ssh-host --ssh-port --ssh-user --ssh-private-key --ssh-host-key --ssh-host-key-vault-id --ssh-host-key-secret-id --ssh-insecure-skip-host-key-verification --schema --encrypt --trust-server-certificate --tls-certificate --host-name-in-certificate --tls-min-version --api-key -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
     --file)
       _postman_filematch '!*.@(json)' "$cur"
       return 0 ;;
+    --driver-jar)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
+    --vars-file)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
+    --java-path)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
     --ssh-private-key)
       _postman_filematch '!*.@(pem|crt|key)' "$cur"
       return 0 ;;
@@ -2102,13 +2126,22 @@ _postman_dataset_source_remove() {
 
 _postman_dataset_source_update() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "-d --dataset -n --name --format --file --ref-only --force --host --port --user --password --database --table --ssh-host --ssh-port --ssh-user --ssh-private-key --ssh-host-key --ssh-host-key-vault-id --ssh-host-key-secret-id --ssh-insecure-skip-host-key-verification --schema --encrypt --trust-server-certificate --tls-certificate --host-name-in-certificate --tls-min-version --api-key -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "-d --dataset -n --name --format --file --ref-only --force --driver-jar --driver-class --driver-name --url-template --var --prop --unset-var --unset-prop --vars-file --ssh-target-host-variable --ssh-target-port-variable --java-path --host --port --user --password --database --table --ssh-host --ssh-port --ssh-user --ssh-private-key --ssh-host-key --ssh-host-key-vault-id --ssh-host-key-secret-id --ssh-insecure-skip-host-key-verification --schema --encrypt --trust-server-certificate --tls-certificate --host-name-in-certificate --tls-min-version --api-key --json -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
     --file)
       _postman_filematch '!*.@(json)' "$cur"
       return 0 ;;
+    --driver-jar)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
+    --vars-file)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
+    --java-path)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
     --ssh-private-key)
       _postman_filematch '!*.@(pem|crt|key)' "$cur"
       return 0 ;;
@@ -2121,6 +2154,21 @@ _postman_dataset_source_update() {
   esac
 }
 
+_postman_dataset_source_test() {
+  if [[ "$cur" == -* ]]; then
+    COMPREPLY=( $(compgen -W "-d --dataset -n --name --java-path --api-key --json -h --help" -- "$cur") )
+    return 0
+  fi
+  case "$prev" in
+    --java-path)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
+    --api-key)
+      _postman_filematch '!*.@(pem|crt|key)' "$cur"
+      return 0 ;;
+  esac
+}
+
 _postman_dataset_view() {
   if [[ -z "$subcmd" ]]; then
     if [[ "$cur" == -* ]]; then
@@ -2165,7 +2213,7 @@ _postman_dataset_view_run() {
 
 _postman_dataset_view_create() {
   if [[ "$cur" == -* ]]; then
-    COMPREPLY=( $(compgen -W "-d --dataset -n --name -q --query --view-id --api-key -h --help" -- "$cur") )
+    COMPREPLY=( $(compgen -W "-d --dataset -n --name -q --query -s --source --view-id --json --api-key -h --help" -- "$cur") )
     return 0
   fi
   case "$prev" in
@@ -2199,6 +2247,32 @@ _postman_dataset_view_update() {
   esac
 }
 
+_postman_dataset_jdbc() {
+  if [[ -z "$subcmd" ]]; then
+    if [[ "$cur" == -* ]]; then
+      COMPREPLY=( $(compgen -W "-h --help" -- "$cur") )
+    else
+      COMPREPLY=( $(compgen -W "inspect" -- "$cur") )
+    fi
+    return 0
+  fi
+  case "$subcmd" in
+    inspect) _postman_dataset_jdbc_inspect ;;
+  esac
+}
+
+_postman_dataset_jdbc_inspect() {
+  if [[ "$cur" == -* ]]; then
+    COMPREPLY=( $(compgen -W "--driver-class --url-template --java-path --json -h --help" -- "$cur") )
+    return 0
+  fi
+  case "$prev" in
+    --java-path)
+      _postman_filematch '!*.@(json)' "$cur"
+      return 0 ;;
+  esac
+}
+
 _postman_dependency() {
   if [[ -z "$subcmd" ]]; then
     if [[ "$cur" == -* ]]; then

package/completions/fish/postman.fish

@@ -1,4 +1,4 @@
-# Fish completion for Postman CLI (postman v1.59.0)
+# Fish 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
@@ -32,7 +32,7 @@ complete -c postman -n __postman_no_subcommand -a collection -d 'Run and test yo
 complete -c postman -n __postman_no_subcommand -a environment -d 'Work with local Postman environments from the command line. Also read cloud environments by ID.'
 complete -c postman -n __postman_no_subcommand -a globals -d 'Work with local Postman globals from the command line.'
 complete -c postman -n __postman_no_subcommand -a api -d 'Publish and test your APIs directly from the command line'
-complete -c postman -n __postman_no_subcommand -a runner -d 'Where your monitors execute: run and inspect your own self-hosted runners, and list the Postman-operated regions available to your team'
+complete -c postman -n __postman_no_subcommand -a runner -d 'Where your monitors execute: run and inspect your own self-hosted runners, and list the Postman-operated regions available to your team.'
 complete -c postman -n __postman_no_subcommand -a spec -d 'Lint and validate Specifications from the command line'
 complete -c postman -n __postman_no_subcommand -a monitor -d 'Run and manage Postman monitors.'
 complete -c postman -n __postman_no_subcommand -a workspace -d 'Manage workspace resources.'
@@ -61,9 +61,7 @@ complete -c postman -n '__fish_seen_subcommand_from login' -l verbose -d 'Show d
 complete -c postman -n '__fish_seen_subcommand_from login' -s h -l help -d 'display help for command'
 
 # ---------- signup ----------
-complete -c postman -n '__fish_seen_subcommand_from signup' -l browser -d 'Always open the sign-up URL in a browser here, rather than printing it.'
-complete -c postman -n '__fish_seen_subcommand_from signup' -l wait -d 'Wait for the sign-up to complete even if no local browser is detected.'
-complete -c postman -n '__fish_seen_subcommand_from signup' -l no-wait -d 'Print the sign-up URL and exit without waiting. Leaves this CLI a guest.'
+complete -c postman -n '__fish_seen_subcommand_from signup' -l guest -d '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`.'
 complete -c postman -n '__fish_seen_subcommand_from signup' -l json -d 'Print the sign-up details as machine-readable JSON.'
 complete -c postman -n '__fish_seen_subcommand_from signup' -s h -l help -d 'display help for command'
 
@@ -87,6 +85,7 @@ complete -c postman -n '__fish_seen_subcommand_from whoami' -l json -d 'Print cu
 complete -c postman -n '__fish_seen_subcommand_from whoami' -s h -l help -d 'display help for command'
 
 # ---------- update ----------
+complete -c postman -n '__fish_seen_subcommand_from update' -l check -d 'Check whether a Postman CLI update is available.'
 complete -c postman -n '__fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
 
 # ---------- skills ----------
@@ -284,22 +283,23 @@ complete -c postman -n '__fish_seen_subcommand_from api; and __fish_seen_subcomm
 complete -c postman -n '__fish_seen_subcommand_from api; and __fish_seen_subcommand_from publish' -s h -l help -d 'display help for command'
 
 # ---------- runner ----------
-complete -c postman -n '__postman_using_subcommand runner start list regions' -a start -d 'Start a runner'
-complete -c postman -n '__postman_using_subcommand runner start list regions' -a list -d 'List the team\'s registered self-hosted runners'
-complete -c postman -n '__postman_using_subcommand runner start list regions' -a regions -d 'List the region and private-runner values valid for monitor create/update --runner, including a static IP where configured'
+complete -c postman -n '__postman_using_subcommand runner start list regions' -a start -d 'Start a self-hosted runner in your own network.'
+complete -c postman -n '__postman_using_subcommand runner start list regions' -a list -d 'List the team\'s registered self-hosted runners.'
+complete -c postman -n '__postman_using_subcommand runner start list regions' -a regions -d '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.'
 complete -c postman -n '__fish_seen_subcommand_from runner' -s h -l help -d 'display help for command'
 # ---------- runner start ----------
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l id -d 'The ID of the runner to execute' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l key -d 'The secret key for the runner' -r
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l region -d 'Specify the region for the runner. Use "eu" for EU region.' -x
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l proxy -d 'External proxy URL (e.g., http://proxy.com or http://proxy.com:8080)' -x
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l region -d 'Region this runner reports to -- use "eu" for the EU region' -x
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l proxy -d 'External proxy URL, for example http://proxy.com or http://proxy.com:8080' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l egress-proxy -d 'Enable built-in egress proxy'
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l egress-proxy-authz-url -d 'Custom egress proxy authorization service base URL' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l ssl-extra-ca-certs -d 'Additional trusted CA certificates (PEM file, can contain multiple certs)' -r
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l dataset-jdbc-driver-dir -d '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' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l metrics -d 'Enable the metrics server for health checks'
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l metrics-port -d 'Port for the metrics server (default: "9090")' -x
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l report-events -d 'Accepted for compatibility; analytics are sent by default'
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l no-report-events -d 'Do not send analytics to Postman'
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l report-events -d 'Accepted for compatibility; run events are reported by default'
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l no-report-events -d 'Do not report run events to Postman'
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -s h -l help -d 'display help for command'
 # ---------- runner list ----------
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
@@ -395,7 +395,7 @@ complete -c postman -n '__postman_using_subcommand monitor run create update del
 complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a resume -d 'Resume a paused monitor, so it fires on schedule again.'
 complete -c postman -n '__fish_seen_subcommand_from monitor' -s h -l help -d 'display help for command'
 # ---------- monitor run ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s x -l suppress-exit-code -d 'Specify whether or not to override the default exit code for the current run'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s t -l timeout -d 'Maximum wait time for run completion in milliseconds (default: 15 minutes) (default: 900000)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l async -d 'Submit the run and return immediately with its job id and Postman URL, without waiting for completion'
@@ -404,14 +404,14 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 # ---------- monitor create ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s c -l collection -d 'Collection to monitor -- accepts the id shown in the Postman app, prefixed or bare' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l name -d 'Monitor name (defaults to the linked collection\'s own name)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l environment -d 'Environment to run the monitored collection with' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s e -l environment -d 'Environment to run the monitored collection with' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s w -l workspace -d 'Workspace to create the monitor in (defaults to the workspace named in the local .postman/resources.yaml manifest; required if neither is available)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l schedule -d 'Cron expression for the monitor\'s schedule' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l timezone -d 'Time zone for --schedule, e.g. America/New_York (defaults to the host machine\'s own zone)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l timezone -d 'Time zone for --schedule, for example America/New_York (defaults to the host machine\'s own zone)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l runner -d '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: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l notify-email -d 'Email to notify on a run failure or error (repeatable) (default: [])' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l notification-limit -d 'Cap consecutive notifications before they are muted (service range: 1-99)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l retry -d 'Retries on a failed run (service caps this at 2)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l notification-limit -d 'Consecutive failure notifications to send before muting them' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l retry -d 'Times to retry a failed run' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l timeout -d 'Request timeout in milliseconds' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l delay -d 'Delay between requests in milliseconds' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l strict-ssl -d 'Fail the run when the target\'s TLS certificate cannot be verified'
@@ -421,7 +421,7 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l dataset-id -d 'Dataset to use as iteration data (used together with --dataset-view-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l dataset-view-id -d 'Dataset view to iterate (used together with --dataset-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l iteration-count -d 'Number of iterations to run' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l iteration-strategy -d 'How iteration data is consumed, e.g. round_robin, repeat_last, stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l iteration-strategy -d 'How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l no-run-now -d 'Do not trigger an immediate run after creating the monitor'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l json -d 'Output as JSON instead of a table'
@@ -429,12 +429,14 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 # ---------- monitor update ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l name -d 'New monitor name' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l schedule -d 'New cron expression for the monitor\'s schedule' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l timezone -d 'Time zone for --schedule, e.g. America/New_York (defaults to the host machine\'s own zone)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l timezone -d 'Time zone for --schedule, for example America/New_York (defaults to the host machine\'s own zone)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l runner -d '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: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l notify-email -d 'Email to notify on a run failure or error (repeatable; replaces the current list) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l clear-notifications -d 'Remove every notification recipient'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l notification-limit -d 'Cap consecutive notifications before they are muted (service range: 1-99)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l retry -d 'Retries on a failed run (service caps this at 2)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -s e -l environment -d 'Environment to run the monitored collection with (replaces the current one)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l clear-environment -d 'Run the monitored collection with no environment'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l notification-limit -d 'Consecutive failure notifications to send before muting them' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l retry -d 'Times to retry a failed run' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l timeout -d 'Request timeout in milliseconds' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l delay -d 'Delay between requests in milliseconds' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l strict-ssl -d 'Fail the run when the target\'s TLS certificate cannot be verified'
@@ -444,7 +446,7 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l dataset-id -d 'Dataset to use as iteration data (used together with --dataset-view-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l dataset-view-id -d 'Dataset view to iterate (used together with --dataset-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l iteration-count -d 'Number of iterations to run' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l iteration-strategy -d 'How iteration data is consumed, e.g. round_robin, repeat_last, stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l iteration-strategy -d 'How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l json -d 'Output as JSON instead of a table'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
@@ -458,24 +460,24 @@ complete -c postman -n '__postman_using_subcommand jobs list get' -a list -d 'Li
 complete -c postman -n '__postman_using_subcommand jobs list get' -a get -d 'Report one job\'s terminal state and its per-region run outcomes.'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs' -s h -l help -d 'display help for command'
 # ---------- monitor jobs list ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l result -d 'Filter by outcome, e.g. success, failure, error, abort (server-validated, not a fixed list)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l trigger -d 'Filter by trigger, e.g. api, schedule, webhook, postman-cli (server-validated, not a fixed list)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l result -d 'Filter by outcome, for example success, failure, error or abort' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l trigger -d 'Filter by trigger, for example api, schedule, webhook or postman-cli' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l since -d 'Only jobs that finished at or after this ISO 8601 date-time' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l limit -d 'Maximum number of jobs to return' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l cursor -d 'Opaque pagination cursor' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l json -d 'Output as JSON instead of a table'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -s h -l help -d 'display help for command'
 # ---------- monitor jobs get ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l json -d 'Output as JSON instead of a table'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- monitor runs ----------
 complete -c postman -n '__postman_using_subcommand runs get' -a get -d 'Report which test assertions ran during one attempt of a run, which failed, and why.'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs' -s h -l help -d 'display help for command'
 # ---------- monitor runs get ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l attempt -d 'Which attempt of the run to show, counting from 0 (default: the latest)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l attempt -d 'Which attempt of the run to show, where 0 is the first (default: the most recent)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l failed-only -d 'Show only failed assertions'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l json -d 'Output as JSON instead of a table'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
@@ -483,15 +485,14 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s w -l workspace -d 'Filter to monitors in this workspace' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s c -l collection -d 'Filter to monitors on this collection' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l environment -d 'Filter to monitors on this environment' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l runner -d 'Filter to a Self-Hosted Runner ID (not a Postman Region). Cannot be combined with --workspace, --collection, --environment, --owner, --team or --active.' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s e -l environment -d 'Filter to monitors on this environment' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l runner -d 'Filter to a self-hosted runner id, not a Postman region. Cannot be combined with --workspace, --collection, --environment, --owner, --team or --active' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l owner -d 'Filter to monitors created by this user id (shown in the Owner column)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l team -d 'Filter to monitors owned by your own team'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l active -d 'Filter by active state' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l limit -d 'Max monitors to return. The service caps page size and rejects a value above it with its own error.' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l offset -d 'Not supported: the service accepts this parameter and silently ignores it. Refused locally. Use --cursor instead.' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l cursor -d 'Pagination cursor from a previous page\'s response.' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l columns -d 'Comma-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available: State, Notifications, Environment, Runners.' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l limit -d 'Maximum number of monitors to return (Postman caps the page size and rejects a larger value)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l cursor -d 'Pagination cursor from a previous page\'s response' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l columns -d 'Comma-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available: State, Notifications, Environment, Runners' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l no-headers -d 'Omit the header row'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s f -l filter -d 'Show only monitors whose name contains this text (applies to the returned page, case-insensitive)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l sort -d 'Sort the returned page by "name" or "active"' -x
@@ -503,10 +504,10 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- monitor metrics ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l since -d 'Only executions at or after this ISO 8601 date-time. Defaults to 7 days ago.' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l until -d 'Only executions at or before this ISO 8601 date-time. Defaults to now.' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l since -d 'Only executions at or after this ISO 8601 date-time (defaults to 7 days ago)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l until -d 'Only executions at or before this ISO 8601 date-time (defaults to now)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -s f -l filter -d 'Show only requests whose name contains this text (case-insensitive)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l limit -d 'Cap the number of rows shown: executions (newest first) under --json, or table rows (worst-behaving request first) otherwise. Not honoured by the service -- there is no server-side pagination on this route.' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l limit -d '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' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l json -d 'Output as JSON instead of a table'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -s h -l help -d 'display help for command'
 # ---------- monitor pause ----------
@@ -519,14 +520,15 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from resume' -s h -l help -d 'display help for command'
 
 # ---------- workspace ----------
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a list -d 'List all available Postman Workspaces'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a prepare -d 'Prepare local collections and environments for push by validating and regenerating IDs if needed.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a push -d 'Push local workspace entities (collections, environments, specifications, mocks and more) to Postman workspace.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a lint -d 'Lint the current local Postman workspace: its configuration (.postman/resources.yaml) plus every discovered entity. Use --meta to lint only the configuration.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a create -d 'Create a Postman workspace and bind it to this git repository.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a pull -d 'Pull workspace entities from a Postman workspace into the local git-native folder.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a connect-git -d 'Connect a Postman workspace to a local git repository.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint create pull connect-git diff' -a diff -d 'Preview local-vs-cloud drift before pushing. Read-only: nothing is created, updated or deleted.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a list -d 'List all available Postman Workspaces'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a prepare -d 'Prepare local collections and environments for push by validating and regenerating IDs if needed.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a push -d 'Push local workspace entities (collections, environments, specifications, mocks and more) to Postman workspace.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a lint -d 'Lint the current local Postman workspace: its configuration (.postman/resources.yaml) plus every discovered entity. Use --meta to lint only the configuration.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a get -d 'Read a workspace\'s metadata, and optionally the ids of what it holds.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a create -d 'Create a Postman workspace and bind it to this git repository.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a pull -d 'Pull workspace entities from a Postman workspace into the local git-native folder.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a connect-git -d 'Connect a Postman workspace to a local git repository.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get create pull connect-git diff' -a diff -d 'Preview local-vs-cloud drift before pushing. Read-only: nothing is created, updated or deleted.'
 complete -c postman -n '__fish_seen_subcommand_from workspace' -s h -l help -d 'display help for command'
 # ---------- workspace list ----------
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from list' -s f -l filter -d 'Filter workspaces by name.' -x
@@ -553,6 +555,11 @@ complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_s
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from lint' -l workspace-id -d 'The workspace ID to use for fetching governance rulesets. Defaults to the id in .postman/resources.yaml.' -x
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from lint' -l fix -d 'Apply safe autofixes to repairable workspace lint issues.'
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from lint' -s h -l help -d 'display help for command'
+# ---------- workspace get ----------
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from get' -l elements -d 'Also report the resources the workspace holds.'
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from get' -l json -d 'Print the workspace as machine-readable JSON.'
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from get' -l timeout -d 'Milliseconds to wait for the API (default 30000).' -x
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- workspace create ----------
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from create' -l visibility -d 'Required. Workspace visibility, e.g. personal or team' -x
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from create' -l name -d 'Workspace name (defaults to owner/repo from the git remote)' -x
@@ -580,8 +587,8 @@ complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_s
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from diff' -s h -l help -d 'display help for command'
 
 # ---------- performance ----------
-complete -c postman -n '__postman_using_subcommand performance run runs' -a run -d 'Run a performance test on a collection'
-complete -c postman -n '__postman_using_subcommand performance run runs' -a runs -d 'List past performance runs for a collection, newest first.'
+complete -c postman -n '__postman_using_subcommand performance run list' -a run -d 'Run a performance test on a collection'
+complete -c postman -n '__postman_using_subcommand performance run list' -a list -d 'List past performance runs for a collection, newest first.'
 complete -c postman -n '__fish_seen_subcommand_from performance' -s h -l help -d 'display help for command'
 # ---------- performance run ----------
 complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from run' -s e -l environment -d 'Specify an Id to a Postman Environment' -x
@@ -601,12 +608,12 @@ complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen
 complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from run' -l use-mock -d 'Redirect a variable/host to a local code mock or cloud Mock Server (repeatable). Format: "<{{var}}|host> mock|mock-server:<path|id> [scenario]" (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from run' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from run' -r -k -a '(__fish_complete_suffix .json)'
-# ---------- performance runs ----------
-complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from runs' -s c -l collection-id -d 'Collection ID whose performance runs to list' -x
-complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from runs' -l cursor -d 'Pagination cursor from a previous page\'s response' -x
-complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from runs' -l json -d 'Output as JSON instead of a table'
-complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from runs' -l timeout -d 'Milliseconds to wait for the service before failing (default: "30000")' -x
-complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from runs' -s h -l help -d 'display help for command'
+# ---------- performance list ----------
+complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from list' -s c -l collection-id -d 'Collection ID whose performance runs to list' -x
+complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from list' -l cursor -d 'Pagination cursor from a previous page\'s response' -x
+complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from list' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from list' -l timeout -d 'Milliseconds to wait for the service before failing (default: "30000")' -x
+complete -c postman -n '__fish_seen_subcommand_from performance; and __fish_seen_subcommand_from list' -s h -l help -d 'display help for command'
 
 # ---------- flows ----------
 complete -c postman -n '__postman_using_subcommand flows list trigger deploy run update list-runs get-run' -a list -d 'List all flows'
@@ -1102,13 +1109,14 @@ complete -c postman -n '__fish_seen_subcommand_from webhook; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from webhook; and __fish_seen_subcommand_from forward' -s h -l help -d 'display help for command'
 
 # ---------- dataset ----------
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a list -d 'List local dataset YAMLs under a path, or (no path) a workspace\'s cloud datasets.'
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a get -d 'Print a dataset\'s metadata and structure summary (local YAML path or cloud id).'
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a query -d 'Run an ad-hoc SQL query against a dataset (local YAML path or cloud id).'
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a create -d 'Scaffold a new .dataset.yaml at <path>, or (no path, with -w) create a cloud dataset.'
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a delete -d 'Permanently remove a dataset: a local .dataset.yaml or a cloud dataset id.'
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a source -d 'Inspect and manage a dataset\'s datasources.'
-complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view' -a view -d 'Inspect and manage saved views on a dataset.'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a list -d 'List local dataset YAMLs under a path, or (no path) a workspace\'s cloud datasets.'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a get -d 'Print a dataset\'s metadata and structure summary (local YAML path or cloud id).'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a query -d 'Run an ad-hoc SQL query against a dataset (local YAML path or cloud id).'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a create -d 'Scaffold a new .dataset.yaml at <path>, or (no path, with -w) create a cloud dataset.'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a delete -d 'Permanently remove a dataset: a local .dataset.yaml or a cloud dataset id.'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a source -d 'Inspect and manage a dataset\'s datasources.'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a view -d 'Inspect and manage saved views on a dataset.'
+complete -c postman -n '__postman_using_subcommand dataset list get query create delete source view jdbc' -a jdbc -d 'Inspect JDBC drivers before attaching one to a dataset.'
 complete -c postman -n '__fish_seen_subcommand_from dataset' -s h -l help -d 'display help for command'
 # ---------- dataset list ----------
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from list' -s w -l workspace -d 'Postman workspace ID (cloud list)' -x
@@ -1144,10 +1152,11 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from delete' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
 # ---------- dataset source ----------
-complete -c postman -n '__postman_using_subcommand source list add remove update' -a list -d 'List the datasources defined on a dataset (local YAML path or cloud id).'
-complete -c postman -n '__postman_using_subcommand source list add remove update' -a add -d 'Add a datasource to a dataset.'
-complete -c postman -n '__postman_using_subcommand source list add remove update' -a remove -d 'Remove a datasource from a dataset (local YAML path or cloud id).'
-complete -c postman -n '__postman_using_subcommand source list add remove update' -a update -d 'Update fields on an existing datasource. Only the flags you provide are changed.'
+complete -c postman -n '__postman_using_subcommand source list add remove update test' -a list -d 'List the datasources defined on a dataset (local YAML path or cloud id).'
+complete -c postman -n '__postman_using_subcommand source list add remove update test' -a add -d 'Add a datasource to a dataset.'
+complete -c postman -n '__postman_using_subcommand source list add remove update test' -a remove -d 'Remove a datasource from a dataset (local YAML path or cloud id).'
+complete -c postman -n '__postman_using_subcommand source list add remove update test' -a update -d 'Update fields on an existing datasource. Only the flags you provide are changed.'
+complete -c postman -n '__postman_using_subcommand source list add remove update test' -a test -d 'Open and close a real connection using a source\'s stored configuration.'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source' -s h -l help -d 'display help for command'
 # ---------- dataset source list ----------
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from list' -s d -l dataset -d 'Dataset whose sources to list — a local .dataset.yaml path or a cloud dataset id' -x
@@ -1159,15 +1168,28 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -s n -l name -d 'Logical name for the source (becomes the SQL table name)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l source-id -d 'Override the generated source id (local dataset only)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l format -d 'Use this format instead of extension/type inference; file contents are not sniffed' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l type -d 'Source kind; local is inferred when --file is provided' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l type -d 'Source kind; local is inferred from --file, jdbc from --driver-jar' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l file -d 'Path to a local CSV/JSON file (absolute or cwd-relative)' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ref-only -d 'Reference the file in place; do NOT copy into data_dir (local dataset)'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l force -d 'When copying, overwrite an existing file at the destination (local dataset)'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l upload -d '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.'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l driver-jar -d 'JDBC driver JAR(s). Repeatable, or pass several after one flag' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l driver-class -d 'Driver class. Auto-resolved when the JAR contains exactly one' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l driver-name -d 'Label for this driver type (defaults to the JAR filename)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l url-template -d 'JDBC URL with {{placeholders}}, e.g. jdbc:postgresql://{{host}}:{{port}}/{{database}}' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l var -d '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.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l prop -d 'Driver connection property. Repeatable. Same vault: syntax as --var' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l vars-file -d 'JSON object of --var values; "-" reads stdin. Supports {"$vaultId":..,"$secretId":..} objects, and keeps secrets out of argv entirely' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l from-source -d 'Reuse another source\'s driver JAR, class and URL template' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l java-path -d 'Java runtime to use. Machine-local only - never written to the dataset. Also read from POSTMAN_JDBC_JAVA_PATH' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l no-test -d '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'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ssh-target-host-variable -d 'Template variable holding the tunnelled host (inferred when omitted)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ssh-target-port-variable -d 'Template variable holding the tunnelled port (inferred when omitted)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l json -d 'Emit the result as JSON instead of prose'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l host -d 'DB host (mysql/postgresql/sqlserver)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l port -d 'DB port (defaults to 1433 for sqlserver)' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l user -d 'DB user (warning: stored as plaintext in the YAML).' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l password -d '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.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l user -d '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.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l password -d '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.' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l database -d 'DB database name' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l table -d 'DB table name (required for sqlserver)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ssh-host -d 'SSH bastion host' -x
@@ -1197,10 +1219,22 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l file -d 'Replace the source file (local dataset only; cloud file replacement is unsupported)' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ref-only -d 'With --file, reference in place instead of copying (local dataset only)'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l force -d 'With --file, overwrite the copied destination (local dataset only)'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l driver-jar -d 'Replace the JDBC driver JAR(s)' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l driver-class -d 'Replace the JDBC driver class' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l driver-name -d 'Rename the JDBC driver type label' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l url-template -d 'Replace the JDBC URL template' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l var -d '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.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l prop -d 'Set a JDBC connection property. Merges, same vault: syntax' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l unset-var -d 'Remove a JDBC template variable. Merging alone can never remove a key' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l unset-prop -d 'Remove a JDBC connection property' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l vars-file -d 'JSON object of --var values; "-" reads stdin' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ssh-target-host-variable -d 'Template variable holding the tunnelled host (JDBC)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ssh-target-port-variable -d 'Template variable holding the tunnelled port (JDBC)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l java-path -d 'Java runtime for JDBC operations. Machine-local only' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l host -d 'Update DB host (mysql/postgresql/sqlserver)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l port -d 'Update DB port' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l user -d 'Update DB user (warning: stored as plaintext in the YAML).' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l password -d '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.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l user -d '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.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l password -d '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.' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l database -d 'Update DB database name' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l table -d 'Update DB table name' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ssh-host -d 'Update SSH bastion host' -x
@@ -1218,7 +1252,15 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l host-name-in-certificate -d 'Update SQL Server certificate hostname override' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l tls-min-version -d 'Update SQL Server minimum TLS version' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l json -d 'Emit the result as JSON instead of prose'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
+# ---------- dataset source test ----------
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from test' -s d -l dataset -d 'Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset id' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from test' -s n -l name -d 'Source to test' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from test' -l java-path -d 'Java runtime to use for a JDBC source. Machine-local only; also read from POSTMAN_JDBC_JAVA_PATH' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from test' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from test' -l json -d 'Emit the result as JSON instead of prose'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from test' -s h -l help -d 'display help for command'
 # ---------- dataset view ----------
 complete -c postman -n '__postman_using_subcommand view list run create delete update' -a list -d 'List the saved views defined on a dataset (local YAML path or cloud id).'
 complete -c postman -n '__postman_using_subcommand view list run create delete update' -a run -d 'Execute a saved view against a dataset and print the rows.'
@@ -1242,7 +1284,9 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -s d -l dataset -d 'Dataset to add the view to — a local .dataset.yaml path or a cloud dataset id' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -s n -l name -d 'View name' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -s q -l query -d 'SQL query the view executes' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -s s -l source -d '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' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -l view-id -d 'Override the generated view id (local only; cloud assigns its own)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -l json -d 'Emit the result as JSON instead of prose'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from create' -s h -l help -d 'display help for command'
 # ---------- dataset view delete ----------
@@ -1255,6 +1299,15 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from update' -s q -l query -d 'New SQL query' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from update' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from view; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
+# ---------- dataset jdbc ----------
+complete -c postman -n '__postman_using_subcommand jdbc inspect' -a inspect -d 'Detect Java, list driver classes, suggest a URL template and read driver properties.'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc' -s h -l help -d 'display help for command'
+# ---------- dataset jdbc inspect ----------
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc; and __fish_seen_subcommand_from inspect' -l driver-class -d 'Introspect this class instead of auto-selecting' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc; and __fish_seen_subcommand_from inspect' -l url-template -d 'Use this URL template instead of the one inferred from the JAR filename' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc; and __fish_seen_subcommand_from inspect' -l java-path -d 'Java runtime to use. Machine-local only — never written to a dataset. Also read from POSTMAN_JDBC_JAVA_PATH.' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc; and __fish_seen_subcommand_from inspect' -l json -d 'Emit the discovery result as JSON'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc; and __fish_seen_subcommand_from inspect' -s h -l help -d 'display help for command'
 
 # ---------- dependency ----------
 complete -c postman -n '__postman_using_subcommand dependency add list install update' -a add -d 'Add a Postman collection, environment, or mock as a workspace dependency.'

package/completions/zsh/_postman

@@ -1,6 +1,6 @@
 #compdef postman
 compdef _postman postman
-# Zsh completion for Postman CLI (postman v1.59.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
@@ -67,7 +67,7 @@ _postman_commands() {
     '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.'
@@ -102,9 +102,7 @@ _postman_login() {
 
 _postman_signup() {
   _arguments \
-    '--browser[Always open the sign-up URL in a browser here, rather than printing it.]' \
-    '--wait[Wait for the sign-up to complete even if no local browser is detected.]' \
-    '--no-wait[Print the sign-up URL and exit without waiting. Leaves this CLI a guest.]' \
+    '--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]'
 }
@@ -136,6 +134,7 @@ _postman_whoami() {
 
 _postman_update() {
   _arguments \
+    '--check[Check whether a Postman CLI update is available.]' \
     '(-h --help)'{-h,--help}'[display help for command]'
 }
 
@@ -553,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
 }
@@ -564,15 +563,16 @@ _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]'
 }
 
@@ -808,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]' \
@@ -821,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]' \
@@ -838,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]' \
@@ -849,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]' \
@@ -864,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]' \
@@ -908,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' \
@@ -921,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:'
@@ -953,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]' \
@@ -966,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' \
@@ -993,10 +994,10 @@ _postman_monitor_get() {
 _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' \
+    '--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[Cap the number of rows shown\: executions (newest first) under --json, or table rows (worst-behaving request first) otherwise. Not honoured by the service -- there is no server-side pagination on this route.]:n' \
+    '--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:'
@@ -1032,6 +1033,7 @@ _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 ;;
@@ -1048,6 +1050,7 @@ _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.'
@@ -1093,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' \
@@ -1143,7 +1155,7 @@ _postman_performance() {
     args)
       case $words[1] in
         run) _postman_performance_run ;;
-        runs) _postman_performance_runs ;;
+        list) _postman_performance_list ;;
       esac
       ;;
   esac
@@ -1153,7 +1165,7 @@ _postman_performance_commands() {
   local -a sub
   sub=(
     'run:Run a performance test on a collection'
-    'runs:List past performance runs for a collection, newest first.'
+    'list:List past performance runs for a collection, newest first.'
   )
   _describe -t commands 'performance command' sub
 }
@@ -1179,7 +1191,7 @@ _postman_performance_run() {
     '*:collectionId:_files -g "*.json"'
 }
 
-_postman_performance_runs() {
+_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' \
@@ -2316,6 +2328,7 @@ _postman_dataset() {
         delete) _postman_dataset_delete ;;
         source) _postman_dataset_source ;;
         view) _postman_dataset_view ;;
+        jdbc) _postman_dataset_jdbc ;;
       esac
       ;;
   esac
@@ -2331,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
 }
@@ -2400,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
@@ -2412,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
 }
@@ -2430,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' \
@@ -2476,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' \
@@ -2497,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
@@ -2557,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]'
 }
@@ -2580,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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli-completion",
-  "version": "1.59.0",
+  "version": "1.60.0",
   "description": "Shell completions for the Postman CLI (zsh, bash, fish)",
   "type": "module",
   "bin": {