From bf9c1bf78b92ca162a49cdfe93a36c9d288256aa Mon Sep 17 00:00:00 2001
From: svc-cli-bot <svc_cli_bot@salesforce.com>
Date: Fri, 29 Sep 2023 16:41:16 +0000
Subject: [PATCH] chore(release): bump to 2.12.2

---
 README.md    | 7714 ++++++++++++++++++++++++++++++++++++++------------
 package.json |    8 +-
 yarn.lock    |   48 +-
 3 files changed, 5940 insertions(+), 1830 deletions(-)

diff --git a/README.md b/README.md
index 06c63175..217e272b 100644
--- a/README.md
+++ b/README.md
@@ -5,11 +5,10 @@
 [![Downloads/week](https://img.shields.io/npm/dw/@salesforce/cli.svg)](https://npmjs.org/package/@salesforce/cli)
 [![License](https://img.shields.io/npm/l/@salesforce/cli.svg)](https://github.com/salesforcecli/cli/blob/master/package.json)
 
-
 # Getting Started
 
 - Read the [sf Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Quick-Introduction-to-Developing-sf-Plugins) to learn how to develop a `sf` plugin.
-- Are you migrating an `sfdx` plugin to `sf`?  Then check out the [migration section](https://github.com/salesforcecli/cli/wiki/Migrate-Plugins-Built-for-sfdx) of the developer guide.
+- Are you migrating an `sfdx` plugin to `sf`? Then check out the [migration section](https://github.com/salesforcecli/cli/wiki/Migrate-Plugins-Built-for-sfdx) of the developer guide.
 - Read [this section of the Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_move_to_sf_v2.htm) for easy instructions on how to move from your `sfdx` (v7) installation to `sf` (v2).
 
 # Feedback
@@ -25,7 +24,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/1.46.0 linux-x64 node-v14.20.0
+@salesforce/cli/2.12.2 linux-x64 node-v18.18.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -42,2821 +41,6711 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 
 <!-- commands -->
 
+- [`sf alias list`](#sf-alias-list)
+- [`sf alias set`](#sf-alias-set)
+- [`sf alias unset`](#sf-alias-unset)
+- [`sf analytics generate template`](#sf-analytics-generate-template)
+- [`sf apex generate class`](#sf-apex-generate-class)
+- [`sf apex generate trigger`](#sf-apex-generate-trigger)
+- [`sf apex get log`](#sf-apex-get-log)
+- [`sf apex get test`](#sf-apex-get-test)
+- [`sf apex list log`](#sf-apex-list-log)
+- [`sf apex run`](#sf-apex-run)
+- [`sf apex run test`](#sf-apex-run-test)
+- [`sf apex tail log`](#sf-apex-tail-log)
 - [`sf autocomplete [SHELL]`](#sf-autocomplete-shell)
+- [`sf commands`](#sf-commands)
 - [`sf config get`](#sf-config-get)
 - [`sf config list`](#sf-config-list)
 - [`sf config set`](#sf-config-set)
 - [`sf config unset`](#sf-config-unset)
-- [`sf deploy`](#sf-deploy)
-- [`sf deploy functions`](#sf-deploy-functions)
-- [`sf deploy metadata`](#sf-deploy-metadata)
-- [`sf deploy metadata cancel`](#sf-deploy-metadata-cancel)
-- [`sf deploy metadata preview`](#sf-deploy-metadata-preview)
-- [`sf deploy metadata quick`](#sf-deploy-metadata-quick)
-- [`sf deploy metadata report`](#sf-deploy-metadata-report)
-- [`sf deploy metadata resume`](#sf-deploy-metadata-resume)
-- [`sf deploy metadata validate`](#sf-deploy-metadata-validate)
-- [`sf env compute collaborator add`](#sf-env-compute-collaborator-add)
-- [`sf env create compute`](#sf-env-create-compute)
-- [`sf env create sandbox`](#sf-env-create-sandbox)
-- [`sf env create scratch`](#sf-env-create-scratch)
-- [`sf env delete`](#sf-env-delete)
-- [`sf env delete sandbox`](#sf-env-delete-sandbox)
-- [`sf env delete scratch`](#sf-env-delete-scratch)
-- [`sf env display`](#sf-env-display)
-- [`sf env list`](#sf-env-list)
-- [`sf env log`](#sf-env-log)
-- [`sf env log tail`](#sf-env-log-tail)
-- [`sf env logdrain add`](#sf-env-logdrain-add)
-- [`sf env logdrain list`](#sf-env-logdrain-list)
-- [`sf env logdrain remove`](#sf-env-logdrain-remove)
-- [`sf env open`](#sf-env-open)
-- [`sf env resume sandbox`](#sf-env-resume-sandbox)
-- [`sf env resume scratch`](#sf-env-resume-scratch)
-- [`sf env var get KEY`](#sf-env-var-get-key)
-- [`sf env var list`](#sf-env-var-list)
-- [`sf env var set`](#sf-env-var-set)
-- [`sf env var unset`](#sf-env-var-unset)
-- [`sf generate function`](#sf-generate-function)
-- [`sf generate metadata field`](#sf-generate-metadata-field)
-- [`sf generate metadata platformevent`](#sf-generate-metadata-platformevent)
-- [`sf generate metadata sobject`](#sf-generate-metadata-sobject)
-- [`sf generate metadata tab`](#sf-generate-metadata-tab)
-- [`sf generate project`](#sf-generate-project)
-- [`sf help [COMMAND]`](#sf-help-command)
-- [`sf info:releasenotes:display [-v <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sf-inforeleasenotesdisplay--v-string---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal)
+- [`sf data create record`](#sf-data-create-record)
+- [`sf data delete bulk`](#sf-data-delete-bulk)
+- [`sf data delete record`](#sf-data-delete-record)
+- [`sf data delete resume`](#sf-data-delete-resume)
+- [`sf data export tree`](#sf-data-export-tree)
+- [`sf data get record`](#sf-data-get-record)
+- [`sf data import tree`](#sf-data-import-tree)
+- [`sf data query`](#sf-data-query)
+- [`sf data query resume`](#sf-data-query-resume)
+- [`sf data resume`](#sf-data-resume)
+- [`sf data update record`](#sf-data-update-record)
+- [`sf data upsert bulk`](#sf-data-upsert-bulk)
+- [`sf data upsert resume`](#sf-data-upsert-resume)
+- [`sf doctor`](#sf-doctor)
+- [`sf force data bulk delete`](#sf-force-data-bulk-delete)
+- [`sf force data bulk status`](#sf-force-data-bulk-status)
+- [`sf force data bulk upsert`](#sf-force-data-bulk-upsert)
+- [`sf force mdapi deploy`](#sf-force-mdapi-deploy)
+- [`sf force mdapi deploy cancel`](#sf-force-mdapi-deploy-cancel)
+- [`sf force mdapi deploy report`](#sf-force-mdapi-deploy-report)
+- [`sf force mdapi retrieve`](#sf-force-mdapi-retrieve)
+- [`sf force mdapi retrieve report`](#sf-force-mdapi-retrieve-report)
+- [`sf force org clone`](#sf-force-org-clone)
+- [`sf force org create`](#sf-force-org-create)
+- [`sf force org delete`](#sf-force-org-delete)
+- [`sf force org status`](#sf-force-org-status)
+- [`sf force source deploy`](#sf-force-source-deploy)
+- [`sf force source deploy cancel`](#sf-force-source-deploy-cancel)
+- [`sf force source deploy report`](#sf-force-source-deploy-report)
+- [`sf force source pull`](#sf-force-source-pull)
+- [`sf force source push`](#sf-force-source-push)
+- [`sf force source retrieve`](#sf-force-source-retrieve)
+- [`sf force source status`](#sf-force-source-status)
+- [`sf force user password generate`](#sf-force-user-password-generate)
+- [`sf help [COMMANDS]`](#sf-help-commands)
+- [`sf info releasenotes display`](#sf-info-releasenotes-display)
+- [`sf lightning generate app`](#sf-lightning-generate-app)
+- [`sf lightning generate component`](#sf-lightning-generate-component)
+- [`sf lightning generate event`](#sf-lightning-generate-event)
+- [`sf lightning generate interface`](#sf-lightning-generate-interface)
+- [`sf lightning generate test`](#sf-lightning-generate-test)
+- [`sf limits api display`](#sf-limits-api-display)
+- [`sf limits recordcounts display`](#sf-limits-recordcounts-display)
 - [`sf login`](#sf-login)
-- [`sf login functions`](#sf-login-functions)
-- [`sf login functions jwt`](#sf-login-functions-jwt)
-- [`sf login org`](#sf-login-org)
-- [`sf login org jwt`](#sf-login-org-jwt)
 - [`sf logout`](#sf-logout)
-- [`sf logout functions`](#sf-logout-functions)
-- [`sf logout org`](#sf-logout-org)
+- [`sf org assign permset`](#sf-org-assign-permset)
+- [`sf org assign permsetlicense`](#sf-org-assign-permsetlicense)
+- [`sf org create sandbox`](#sf-org-create-sandbox)
+- [`sf org create scratch`](#sf-org-create-scratch)
+- [`sf org create user`](#sf-org-create-user)
+- [`sf org delete sandbox`](#sf-org-delete-sandbox)
+- [`sf org delete scratch`](#sf-org-delete-scratch)
+- [`sf org display`](#sf-org-display)
+- [`sf org display user`](#sf-org-display-user)
+- [`sf org generate password`](#sf-org-generate-password)
+- [`sf org list`](#sf-org-list)
+- [`sf org list auth`](#sf-org-list-auth)
+- [`sf org list metadata`](#sf-org-list-metadata)
+- [`sf org list metadata-types`](#sf-org-list-metadata-types)
+- [`sf org list users`](#sf-org-list-users)
+- [`sf org login access-token`](#sf-org-login-access-token)
+- [`sf org login device`](#sf-org-login-device)
+- [`sf org login jwt`](#sf-org-login-jwt)
+- [`sf org login sfdx-url`](#sf-org-login-sfdx-url)
+- [`sf org login web`](#sf-org-login-web)
+- [`sf org logout`](#sf-org-logout)
+- [`sf org open`](#sf-org-open)
+- [`sf org resume sandbox`](#sf-org-resume-sandbox)
+- [`sf org resume scratch`](#sf-org-resume-scratch)
 - [`sf plugins`](#sf-plugins)
-- [`sf plugins:install PLUGIN...`](#sf-pluginsinstall-plugin)
+- [`sf plugins discover`](#sf-plugins-discover)
 - [`sf plugins:inspect PLUGIN...`](#sf-pluginsinspect-plugin)
-- [`sf plugins:install PLUGIN...`](#sf-pluginsinstall-plugin-1)
+- [`sf plugins:install PLUGIN...`](#sf-pluginsinstall-plugin)
 - [`sf plugins:link PLUGIN`](#sf-pluginslink-plugin)
+- [`sf plugins trust verify`](#sf-plugins-trust-verify)
 - [`sf plugins:uninstall PLUGIN...`](#sf-pluginsuninstall-plugin)
-- [`sf plugins:trust:verify -n <string> [-r <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sf-pluginstrustverify--n-string--r-string---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal)
-- [`sf plugins:uninstall PLUGIN...`](#sf-pluginsuninstall-plugin-1)
-- [`sf plugins:uninstall PLUGIN...`](#sf-pluginsuninstall-plugin-2)
 - [`sf plugins update`](#sf-plugins-update)
-- [`sf retrieve metadata`](#sf-retrieve-metadata)
-- [`sf retrieve metadata preview`](#sf-retrieve-metadata-preview)
-- [`sf run function`](#sf-run-function)
-- [`sf run function start`](#sf-run-function-start)
-- [`sf run function start container`](#sf-run-function-start-container)
-- [`sf run function start local`](#sf-run-function-start-local)
+- [`sf project convert mdapi`](#sf-project-convert-mdapi)
+- [`sf project convert source`](#sf-project-convert-source)
+- [`sf project delete source`](#sf-project-delete-source)
+- [`sf project delete tracking`](#sf-project-delete-tracking)
+- [`sf project deploy cancel`](#sf-project-deploy-cancel)
+- [`sf project deploy preview`](#sf-project-deploy-preview)
+- [`sf project deploy quick`](#sf-project-deploy-quick)
+- [`sf project deploy report`](#sf-project-deploy-report)
+- [`sf project deploy resume`](#sf-project-deploy-resume)
+- [`sf project deploy start`](#sf-project-deploy-start)
+- [`sf project deploy validate`](#sf-project-deploy-validate)
+- [`sf project generate`](#sf-project-generate)
+- [`sf project generate manifest`](#sf-project-generate-manifest)
+- [`sf project list ignored`](#sf-project-list-ignored)
+- [`sf project reset tracking`](#sf-project-reset-tracking)
+- [`sf project retrieve preview`](#sf-project-retrieve-preview)
+- [`sf project retrieve start`](#sf-project-retrieve-start)
+- [`sf schema generate field`](#sf-schema-generate-field)
+- [`sf schema generate platformevent`](#sf-schema-generate-platformevent)
+- [`sf schema generate sobject`](#sf-schema-generate-sobject)
+- [`sf schema generate tab`](#sf-schema-generate-tab)
 - [`sf search`](#sf-search)
+- [`sf sobject describe`](#sf-sobject-describe)
+- [`sf sobject list`](#sf-sobject-list)
+- [`sf static-resource generate`](#sf-static-resource-generate)
 - [`sf update [CHANNEL]`](#sf-update-channel)
 - [`sf version`](#sf-version)
-- [`sf whatsnew [-v <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sf-whatsnew--v-string---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal)
-- [`sf whoami functions`](#sf-whoami-functions)
+- [`sf visualforce generate component`](#sf-visualforce-generate-component)
+- [`sf visualforce generate page`](#sf-visualforce-generate-page)
+- [`sf which`](#sf-which)
 
-## `sf autocomplete [SHELL]`
+## `sf alias list`
 
-display autocomplete installation instructions
+List all aliases currently set on your local computer.
 
 ```
 USAGE
-  $ sf autocomplete [SHELL] [-r]
+  $ sf alias list [--json]
 
-ARGUMENTS
-  SHELL  shell type
+GLOBAL FLAGS
+  --json  Format output as json.
 
-FLAGS
-  -r, --refresh-cache  Refresh cache (ignores displaying instructions)
+DESCRIPTION
+  List all aliases currently set on your local computer.
+
+  Aliases are global, which means that you can use all the listed aliases in any Salesforce DX project on your computer.
+
+ALIASES
+  $ sf force alias list
+
+EXAMPLES
+  List all the aliases you've set:
+
+    $ sf alias list
+```
+
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/alias/list.ts)_
+
+## `sf alias set`
+
+Set one or more aliases on your local computer.
+
+```
+USAGE
+  $ sf alias set [--json]
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  display autocomplete installation instructions
+  Set one or more aliases on your local computer.
+
+  Aliases are user-defined short names that make it easier to use the CLI. For example, users often set an alias for a
+  scratch org usernames because they're long and unintuitive.  Check the --help of a CLI command to determine where you
+  can use an alias.
+
+  You can associate an alias with only one value at a time. If you set an alias multiple times, the alias points to the
+  most recent value. Aliases are global; after you set an alias, you can use it in any Salesforce DX project on your
+  computer.
+
+  Use quotes to specify an alias value that contains spaces. You typically use an equal sign to set your alias, although
+  you don't need it if you're setting a single alias in a command.
+
+ALIASES
+  $ sf force alias set
 
 EXAMPLES
-  $ sf autocomplete
+  Set an alias for a scratch org username:
 
-  $ sf autocomplete bash
+    $ sf alias set my-scratch-org=test-sadbiytjsupn@example.com
 
-  $ sf autocomplete zsh
+  Set multiple aliases with a single command:
 
-  $ sf autocomplete --refresh-cache
+    $ sf alias set my-scratch-org=test-sadbiytjsupn@example.com my-other-scratch-org=test-ss0xut7txzxf@example.com
+
+  Set an alias that contains spaces:
+
+    $ sf alias set my-alias='alias with spaces'
+
+  Set a single alias without using an equal sign:
+
+    $ sf alias set my-scratch-org test-ss0xut7txzxf@example.com
 ```
 
-_See code: [@oclif/plugin-autocomplete](https://github.com/oclif/plugin-autocomplete/blob/v1.3.0/src/commands/autocomplete/index.ts)_
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/alias/set.ts)_
 
-## `sf config get`
+## `sf alias unset`
 
-Get the value of a configuration variable.
+Unset one or more aliases that are currently set on your local computer.
 
 ```
 USAGE
-  $ sf config get [--json] [--verbose]
+  $ sf alias unset [--json] [-a] [-p]
 
 FLAGS
-  --verbose  Display whether the configuration variables are set locally or globally.
+  -a, --all        Unset all currently set aliases.
+  -p, --no-prompt  Don't prompt the user for confirmation when unsetting all aliases.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Get the value of a configuration variable.
+  Unset one or more aliases that are currently set on your local computer.
 
-  Run "sf config list" to see all the configuration variables you've set. Global configuration variable are always
-  displayed; local ones are displayed if you run the command in a project directory. Run "sf config set" to set a
-  configuration variable.
+  Aliases are global, so when you unset one it's no longer available in any Salesforce DX project.
+
+ALIASES
+  $ sf force alias unset
 
 EXAMPLES
-  Get the value of the "target-org" configuration variable.
+  Unset an alias:
 
-    $ sf config get target-org
+    $ sf alias unset my-alias
 
-  Get multiple configuration variables and display whether they're set locally or globally:
+  Unset multiple aliases with a single command:
 
-    $ sf config get target-org api-version --verbose
+    $ sf alias unset my-alias my-other-alias
 
-CONFIGURATION VARIABLES
-  apiVersion        API version of your project. Default: API version of your Dev Hub org. (sfdx only)
-  disableTelemetry  Disables the collection of usage and user environment information, etc. Default: false. (sfdx only)
-  instanceUrl       URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com. (sfdx only)
-  maxQueryLimit     Maximum number of Salesforce records returned by a CLI command. Default: 10,000. (sfdx only)
-  restDeploy        Whether deployments use the Metadata REST API (true) or SOAP API (false, default value). (sfdx only)
-  target-org        Username or alias of the org that all commands run against by default. (sf only)
-  target-dev-hub    Username or alias of your default Dev Hub org. (sf only)
+  Unset all aliases:
+
+    $ sf alias unset --all [--no-prompt]
 ```
 
-## `sf config list`
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/alias/unset.ts)_
 
-List the configuration variables that you've previously set.
+## `sf analytics generate template`
+
+Generate a simple Analytics template.
 
 ```
 USAGE
-  $ sf config list [--json]
+  $ sf analytics generate template -n <value> [--json] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the Analytics template.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List the configuration variables that you've previously set.
+  Generate a simple Analytics template.
+
+  The metadata files associated with the Analytics template must be contained in a parent directory called
+  "waveTemplates" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
 
-  Global configuration variables apply to any directory and are always displayed. If you run this command from a project
-  directory, local configuration variables are also displayed.
+ALIASES
+  $ sf force analytics template create
 
 EXAMPLES
-  List both global configuration variables and those local to your project:
+  Generate the metadata files for a simple Analytics template file called myTemplate in the
+  force-app/main/default/waveTemplates directory:
 
-    $ sf config list
+    $ sf analytics generate template --name myTemplate --output-dir force-app/main/default/waveTemplates
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 ```
 
-## `sf config set`
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/analytics/generate/template.ts)_
 
-Set one or more configuration variables, such as your default org.
+## `sf apex generate class`
+
+Generate an Apex class.
 
 ```
 USAGE
-  $ sf config set [--json] [-g]
+  $ sf apex generate class -n <value> [--json] [-t ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService] [-d
+    <value>] [--api-version <value>]
 
 FLAGS
-  -g, --global  Set the configuration variables globally, so they can be used from any directory.
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated Apex class.
+  -t, --template=<option>   [default: DefaultApexClass] Template to use for file creation.
+                            <options: ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService>
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Set one or more configuration variables, such as your default org.
-
-  Use configuration variables to set CLI defaults, such as your default org or the API version you want the CLI to use.
-  For example, if you set the "target-org" configuration variable, you don't need to specify it as a "sf deploy
-  metadata" flag if you're deploying to your default org.
-
-  Local configuration variables apply only to your current project. Global variables, specified with the --global flag,
-  apply in any directory.
+  Generate an Apex class.
 
-  The resolution order if you've set a flag value in multiple ways is as follows:
+  Generates the Apex *.cls file and associated metadata file. These files must be contained in a parent directory called
+  "classes" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
 
-  1. Flag value specified at the command line.
+ALIASES
+  $ sf force apex class create
 
-  2. Local (project-level) configuration variable.
+EXAMPLES
+  Generate two metadata files associated with the MyClass Apex class (MyClass.cls and MyClass.cls-meta.xml) in the
+  current directory:
 
-  3. Global configuration variable.
+    $ sf apex generate class --name MyClass
 
-  Run "sf config list" to see the configuration variables you've already set and their level (local or global).
+  Similar to previous example, but generates the files in the "force-app/main/default/classes" directory:
 
-EXAMPLES
-  Set the local target-org configuration variable to an org username:
+    $ sf apex generate class --name MyClass --output-dir force-app/main/default/classes
 
-    $ sf config set target-org=me@my.org
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
 
-  Set the local target-org configuration variable to an alias:
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 
-    $ sf config set target-org=my-scratch-org
+  -n, --name=<value>  Name of the generated Apex class.
 
-  Set the global target-org configuration variable:
+    The name can be up to 40 characters and must start with a letter.
 
-    $ sf config set --global target-org=my-scratch-org
+  -t, --template=ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService  Template to use for file creation.
 
-CONFIGURATION VARIABLES
-  apiVersion        API version of your project. Default: API version of your Dev Hub org. (sfdx only)
-  disableTelemetry  Disables the collection of usage and user environment information, etc. Default: false. (sfdx only)
-  instanceUrl       URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com. (sfdx only)
-  maxQueryLimit     Maximum number of Salesforce records returned by a CLI command. Default: 10,000. (sfdx only)
-  restDeploy        Whether deployments use the Metadata REST API (true) or SOAP API (false, default value). (sfdx only)
-  target-org        Username or alias of the org that all commands run against by default. (sf only)
-  target-dev-hub    Username or alias of your default Dev Hub org. (sf only)
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-## `sf config unset`
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/apex/generate/class.ts)_
 
-Unset local or global configuration variables.
+## `sf apex generate trigger`
+
+Generate an Apex trigger.
 
 ```
 USAGE
-  $ sf config unset [--json] [-g]
+  $ sf apex generate trigger -n <value> [--json] [-t ApexTrigger] [-d <value>] [--api-version <value>] [-s <value>] [-e
+    before insert|before update|before delete|after insert|after update|after delete|after undelete]
 
 FLAGS
-  -g, --global  Unset the configuration variables globally, so they can no longer be used from any directory.
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -e, --event=<option>...   [default: before insert] Events that fire the trigger.
+                            <options: before insert|before update|before delete|after insert|after update|after
+                            delete|after undelete>
+  -n, --name=<value>        (required) Name of the generated Apex trigger
+  -s, --sobject=<value>     [default: SOBJECT] Salesforce object to generate a trigger on.
+  -t, --template=<option>   [default: ApexTrigger] Template to use for file creation.
+                            <options: ApexTrigger>
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Unset local or global configuration variables.
+  Generate an Apex trigger.
 
-  Local configuration variables apply only to your current project. Global configuration variables apply in any
-  directory.
+  Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent
+  directory called "triggers" in your package directory. Either run this command from an existing directory of this
+  name, or use the --output-dir flag to generate one or point to an existing one.
+
+  If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with
+  the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
+
+ALIASES
+  $ sf force apex trigger create
 
 EXAMPLES
-  Unset the local "target-org" configuration variable:
+  Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in
+  the current directory:
 
-    $ sf config unset target-org
+    $ sf apex generate trigger --name MyTrigger
 
-  Unset multiple configuration variables globally:
+  Similar to the previous example, but generate the files in the "force-app/main/default/triggers" directory:
 
-    $ sf config unset target-org api-version --global
+    $ sf apex generate trigger --name MyTrigger --output-dir force-app/main/default/triggers
 
-CONFIGURATION VARIABLES
-  apiVersion        API version of your project. Default: API version of your Dev Hub org. (sfdx only)
-  disableTelemetry  Disables the collection of usage and user environment information, etc. Default: false. (sfdx only)
-  instanceUrl       URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com. (sfdx only)
-  maxQueryLimit     Maximum number of Salesforce records returned by a CLI command. Default: 10,000. (sfdx only)
-  restDeploy        Whether deployments use the Metadata REST API (true) or SOAP API (false, default value). (sfdx only)
-  target-org        Username or alias of the org that all commands run against by default. (sf only)
-  target-dev-hub    Username or alias of your default Dev Hub org. (sf only)
+  Generate files for a trigger that fires on the Account object before and after an insert:
+
+    $ sf apex generate trigger --name MyTrigger --sobject Account --event "before insert,after insert"
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Apex trigger
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=ApexTrigger  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-## `sf deploy`
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/apex/generate/trigger.ts)_
+
+## `sf apex get log`
 
-Deploy a project interactively to any Salesforce environment.
+Fetch the specified log or given number of most recent logs from the org.
 
 ```
 USAGE
-  $ sf deploy [--interactive]
+  $ sf apex get log -o <value> [--json] [--api-version <value>] [-i <value>] [-n <value>] [-d <value>]
 
 FLAGS
-  --interactive  Force the CLI to prompt for all deployment inputs.
+  -d, --output-dir=<value>  Directory for saving the log files.
+  -i, --log-id=<value>      ID of the specific log to display.
+  -n, --number=<value>      Number of the most recent logs to display.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Deploy a project interactively to any Salesforce environment.
+  Fetch the specified log or given number of most recent logs from the org.
 
-  This command must be run from within a project.
+  To get the IDs for your debug logs, run "sf apex log list". Executing this command without flags returns the most
+  recent log.
 
-  The command first analyzes your project, your active or logged-into environments, and local defaults to determine what
-  to deploy and where to deploy it. The command then prompts you for information about this particular deployment and
-  provides intelligent choices based on its analysis.
+ALIASES
+  $ sf force apex log get
 
-  For example, if your local project contains a source directory with metadata files in source format, the command asks
-  if you want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want
-  to deploy to. The list of orgs starts with scratch orgs, ordered by expiration date with the most recently created one
-  first, and then Dev Hub and production orgs ordered by name. If the command finds Apex tests, it asks if you want to
-  run them and at which level.
+EXAMPLES
+  Fetch the log in your default org using an ID:
 
-  The command stores your responses in the "deploy-options.json" file in your local project directory and uses them as
-  defaults when you rerun the command. Specify --interactive to force the command to reprompt.
+    $ sf apex get log --log-id <log id>
 
-  Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific
-  commands, such as "sf deploy metadata", that provide additional flags.
+  Fetch the log in the org with the specified username using an ID:
 
-EXAMPLES
-  Deploy a project and use stored values from a previous command run:
+    $ sf apex get log --log-id <log id> --target-org me@my.org
 
-    $ sf deploy
+  Fetch the two most recent logs in your default org:
 
-  Reprompt for all deployment inputs:
+    $ sf apex get log --number 2
 
-    $ sf deploy --interactive
+  Similar to previous example, but save the two log files in the specified directory:
+
+    $ sf apex get log --output-dir /Users/sfdxUser/logs --number 2
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the log files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 ```
 
-_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/v1.6.1/src/commands/deploy.ts)_
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/2.3.16/src/commands/apex/get/log.ts)_
 
-## `sf deploy functions`
+## `sf apex get test`
 
-Deploy a Salesforce Function to an org from your local project.
+Display test results for a specific asynchronous test run.
 
 ```
 USAGE
-  $ sf deploy functions -o <value> [--json] [-b <value>] [--force] [-q]
+  $ sf apex get test -o <value> -i <value> [--json] [--api-version <value>] [-c] [-d <value>] [-r
+    human|tap|junit|json]
 
 FLAGS
-  -b, --branch=<value>         Deploy the latest commit from a branch different from the currently active branch.
-  -o, --connected-org=<value>  (required) Username or alias for the org that the compute environment should be connected
-                               to.
-  -q, --quiet                  Limit the amount of output displayed from the deploy process.
-  --force                      Ignore warnings and overwrite remote repository (not allowed in production).
+  -c, --code-coverage           Retrieve code coverage results.
+  -d, --output-dir=<value>      Directory in which to store test result files.
+  -i, --test-run-id=<value>     (required) ID of the test run.
+  -o, --target-org=<value>      (required) Username or alias of the target org.
+  -r, --result-format=<option>  [default: human] Format of the results.
+                                <options: human|tap|junit|json>
+  --api-version=<value>         Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Deploy a Salesforce Function to an org from your local project.
+  Display test results for a specific asynchronous test run.
 
-  You must run this command from within a git repository. Only committed changes to Functions are deployed. The active
-  branch is deployed unless specified otherwise with `--branch`.
+  Provide a test run ID to display test results for an enqueued or completed asynchronous test run. The test run ID is
+  displayed after running the "sf apex test run" command.
+
+ALIASES
+  $ sf force apex test report
 
 EXAMPLES
-  Deploy a Salesforce Function:
+  Display test results for your default org using a test run ID:
+
+    $ sf apex get test --test-run-id <test run id>
+
+  Similar to previous example, but output the result in JUnit format:
 
-    $ sf deploy functions --connected-org org-alias
+    $ sf apex get test --test-run-id <test run id> --result-format junit
 
-  Deploy to 'deploy-branch':
+  Also retrieve code coverage results and output in JSON format:
 
-    $ sf deploy functions --connected-org org-alias --branch deploy-branch
+    $ sf apex get test --test-run-id <test run id> --code-coverage --json
 
-  Overwrite the remote repository:
+  Specify a directory in which to save the test results from the org with the specified username (rather than your
+  default org):
 
-    $ sf deploy functions --connected-org org-alias --force
+    $ sf apex get test --test-run-id <test run id> --code-coverage --output-dir <path to outputdir> --target-org \
+      me@myorg',
 ```
 
-## `sf deploy metadata`
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/2.3.16/src/commands/apex/get/test.ts)_
 
-Deploy metadata to an org from your local project.
+## `sf apex list log`
+
+Display a list of IDs and general information about debug logs.
 
 ```
 USAGE
-  $ sf deploy metadata [--json] [-a <value>] [--async | -w <value>] [--concise | --verbose] [--dry-run] [-c] [-r]
-    [-g] [-x <value> | -d <value> | -m <value> | --metadata-dir <value>] [--single-package ] [-o <value>] [-t <value>]
-    [-l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg]
+  $ sf apex list log -o <value> [--json] [--api-version <value>]
 
 FLAGS
-  -a, --api-version=<value>    Target API version for the deploy.
-  -c, --ignore-conflicts       Ignore conflicts and deploy local files, even if they overwrite changes in the org.
-  -d, --source-dir=<value>...  Path to the local source files to deploy.
-  -g, --ignore-warnings        Ignore warnings and allow a deployment to complete successfully.
-  -l, --test-level=<option>    [default: NoTestRun] Deployment Apex testing level.
-                               <options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
-  -m, --metadata=<value>...    Metadata component names to deploy.
-  -o, --target-org=<value>     Login username or alias for the target org.
-  -r, --ignore-errors          Ignore any errors and don’t roll back deployment.
-  -t, --tests=<value>...       Apex tests to run when --test-level is RunSpecifiedTests.
-  -w, --wait=<minutes>         Number of minutes to wait for command to complete and display results.
-  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to deploy.
-  --async                      Run the command asynchronously.
-  --concise                    Show concise output of the deploy result.
-  --dry-run                    Validate deploy and run Apex tests but don’t save to the org.
-  --metadata-dir=<value>       Root of directory or zip file of metadata formatted files to deploy.
-  --single-package             Indicates that the metadata zip file points to a directory structure for a single
-                               package.
-  --verbose                    Show verbose output of the deploy result.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Deploy metadata to an org from your local project.
-
-  You must run this command from within a project.
+  Display a list of IDs and general information about debug logs.
 
-  Metadata components are deployed in source format by default. Deploy them in metadata format by specifying the
-  --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you
-  want to deploy.
+  Run this command in a project to list the IDs and general information for all debug logs in your default org.
 
-  If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production
-  org, never allow source tracking. You can also use the "--no-track-source" flag when you create a scratch or sandbox
-  org to disable source tracking.
+  To fetch a specific log from your org, obtain the ID from this command's output, then run the “sf apex log get”
+  command.
 
-  To deploy multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with
-  multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax
-  applies to --manifest and --source-dir.
+ALIASES
+  $ sf force apex log list
 
 EXAMPLES
-  Deploy local changes not in the org:
+  List the IDs and information about the debug logs in your default org:
 
-    $ sf deploy metadata
+    $ sf apex list log
 
-  Deploy the source files in a directory:
+  Similar to previous example, but use the org with the specified username:
 
-    $ sf deploy metadata  --source-dir path/to/source
+    $ sf apex list log --target-org me@my.org
+```
 
-  Deploy a specific Apex class and the objects whose source is in a directory (both examples are equivalent):
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/2.3.16/src/commands/apex/list/log.ts)_
 
-    $ sf deploy metadata --source-dir path/to/apex/classes/MyClass.cls path/to/source/objects
-    $ sf deploy metadata --source-dir path/to/apex/classes/MyClass.cls --source-dir path/to/source/objects
+## `sf apex run`
 
-  Deploy all Apex classes:
+Execute anonymous Apex code entered on the command line or from a local file.
 
-    $ sf deploy metadata --metadata ApexClass
+```
+USAGE
+  $ sf apex run -o <value> [--json] [--api-version <value>] [-f <value>]
 
-  Deploy a specific Apex class:
+FLAGS
+  -f, --file=<value>        Path to a local file that contains Apex code.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
-    $ sf deploy metadata --metadata ApexClass:MyApexClass
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  Deploy all custom objects and Apex classes (both examples are equivalent):
+DESCRIPTION
+  Execute anonymous Apex code entered on the command line or from a local file.
 
-    $ sf deploy metadata --metadata CustomObject ApexClass
-    $ sf deploy metadata --metadata CustomObject --metadata ApexClass
+  If you don’t run this command from within a Salesforce DX project, you must specify the —-target-org flag.
 
-  Deploy all Apex classes and a profile that has a space in its name:
+  To execute your code interactively, run this command with no flags. At the prompt, enter all your Apex code; press
+  CTRL-D when you're finished. Your code is then executed in a single execute anonymous request.
+  For more information, see "Anonymous Blocks" in the Apex Developer Guide.
 
-    $ sf deploy metadata --metadata ApexClass --metadata "Profile:My Profile"
+ALIASES
+  $ sf force apex execute
 
-  Deploy all components listed in a manifest:
+EXAMPLES
+  Execute the Apex code that's in the ~/test.apex file in the org with the specified username:
 
-    $ sf deploy metadata --manifest path/to/package.xml
+    $ sf apex run --target-org testusername@salesforce.org --file ~/test.apex
 
-  Run the tests that aren’t in any managed packages as part of a deployment:
+  Similar to previous example, but execute the code in your default org:
 
-    $ sf deploy metadata --metadata ApexClass --test-level RunLocalTests
+    $ sf apex run --file ~/test.apex
 
-FLAG DESCRIPTIONS
-  -a, --api-version=<value>  Target API version for the deploy.
+  Run the command with no flags to start interactive mode; the code will execute in your default org when you exit. At
+  the prompt, start type Apex code and press the Enter key after each line. Press CTRL+D when finished.
 
-    Use this flag to override the default API version with the API version of your package.xml file. The default API
-    version is the latest version supported by the CLI.
+    $ sf apex run
+```
 
-  -c, --ignore-conflicts  Ignore conflicts and deploy local files, even if they overwrite changes in the org.
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/2.3.16/src/commands/apex/run.ts)_
 
-    This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as
-    production orgs.
+## `sf apex run test`
 
-  -d, --source-dir=<value>...  Path to the local source files to deploy.
+Invoke Apex tests in an org.
 
-    The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder
-    (in which case the operation is applied to all metadata types in the directory and its subdirectories).
+```
+USAGE
+  $ sf apex run test -o <value> [--json] [--api-version <value>] [-d <value>] [-l
+    RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests] [-n <value> | -s <value> | -t <value>] [-r human|tap|junit|json]
+    [-w <value>] [-y] [-v -c]
 
-    If you specify this flag, don’t specify --metadata or --manifest.
+FLAGS
+  -c, --code-coverage           Retrieve code coverage results.
+  -d, --output-dir=<value>      Directory in which to store test run files.
+  -l, --test-level=<option>     Level of tests to run; default is RunLocalTests.
+                                <options: RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests>
+  -n, --class-names=<value>...  Apex test class names to run; default is all classes.
+  -o, --target-org=<value>      (required) Username or alias of the target org.
+  -r, --result-format=<option>  [default: human] Format of the test results.
+                                <options: human|tap|junit|json>
+  -s, --suite-names=<value>...  Apex test suite names to run; default is all suites.
+  -t, --tests=<value>...        Apex test class names or IDs and, if applicable, test methods to run; default is all
+                                tests.
+  -v, --detailed-coverage       Display detailed code coverage per test.
+  -w, --wait=<value>            Sets the streaming client socket timeout in minutes; specify a longer wait time if
+                                timeouts occur frequently.
+  -y, --synchronous             Runs test methods from a single Apex class synchronously; if not specified, tests are
+                                run asynchronously.
+  --api-version=<value>         Override the api version used for api requests made by this command
 
-  -g, --ignore-warnings  Ignore warnings and allow a deployment to complete successfully.
+GLOBAL FLAGS
+  --json  Format output as json.
 
-    If a warning occurs and this flag is set to true, the success status of the deployment is set to true. When this
-    flag is set to false, success is set to false, and the warning is treated like an error.
+DESCRIPTION
+  Invoke Apex tests in an org.
 
-  -l, --test-level=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg  Deployment Apex testing level.
+  Specify which tests to run by using the --class-names, --suite-names, or --tests flags. Alternatively, use the
+  --test-level flag to run all the tests in your org, local tests, or specified tests.
 
-    Valid values are:
+  To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level
+  summary of the test run and the code coverage values for classes in your org. If you specify human-readable result
+  format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
 
-    - NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as
-    sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.
+  By default, Apex tests run asynchronously and immediately return a test run ID. You can use the --wait flag to specify
+  the number of minutes to wait; if the tests finish in that timeframe, the command displays the results. If the tests
+  haven't finished by the end of the wait time, the command displays a test run ID. Use the "sf apex get test
+  --test-run-id" command to get the results.
 
-    - RunSpecifiedTests — Runs only the tests that you specify with the --run-tests flag. Code coverage requirements
-    differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of
-    75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
-    trigger individually and is different than the overall coverage percentage.
+  NOTE: The testRunCoverage value (JSON and JUnit result formats) is a percentage of the covered lines and total lines
+  from all the Apex classes evaluated by the tests in this run.
 
-    - RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked
-    packages. This test level is the default for production deployments that include Apex classes or triggers.
+ALIASES
+  $ sf force apex test run
 
-    - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
+EXAMPLES
+  Run all Apex tests and suites in your default org:
 
-    If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more
-    information, see [Running Tests in a
-    Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)
-    in the "Metadata API Developer Guide".
+    $ sf apex run test
 
-  -o, --target-org=<value>  Login username or alias for the target org.
+  Run the specified Apex test classes in your default org and display results in human-readable form:
 
-    Overrides your default org.
+    $ sf apex run test --class-names MyClassTest --class-names MyOtherClassTest --result-format human
 
-  -r, --ignore-errors  Ignore any errors and don’t roll back deployment.
+  Run the specified Apex test suites in your default org and include code coverage results and additional details:
 
-    When deploying to a production org, keep this flag set to false (default value). When set to true, components
-    without errors are deployed and components with errors are skipped, and could result in an inconsistent production
-    org.
+    $ sf apex run test --suite-names MySuite --suite-names MyOtherSuite --code-coverage --detailed-coverage
 
-  -t, --tests=<value>...  Apex tests to run when --test-level is RunSpecifiedTests.
+  Run the specified Apex tests in your default org and display results in human-readable output:
 
-    Separate multiple test names with commas, and enclose the entire flag value in double quotes if a test contains a
-    space.
+    $ sf apex run test --tests MyClassTest.testCoolFeature --tests MyClassTest.testAwesomeFeature --tests \
+      AnotherClassTest --tests namespace.TheirClassTest.testThis --result-format human
 
-  -w, --wait=<minutes>  Number of minutes to wait for command to complete and display results.
+  Run all tests in the org with the specified username with the specified test level; save the output to the specified
+  directory:
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
-    returns the job ID. To resume the deployment, run "sf deploy metadata resume". To check the status of the
-    deployment, run "sf deploy metadata report".
+    $ sf apex run test --test-level RunLocalTests --output-dir <path to outputdir> --target-org me@my.org
 
-  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to deploy.
+FLAG DESCRIPTIONS
+  -l, --test-level=RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests  Level of tests to run; default is RunLocalTests.
 
-    All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
+    Here's what the levels mean:
 
-  --async  Run the command asynchronously.
+    - RunSpecifiedTests — Only the tests that you specify are run.
+    - RunLocalTests — All tests in your org are run, except the ones that originate from installed managed packages.
+    - RunAllTestsInOrg — All tests are in your org and in installed managed packages are run
 
-    The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the
-    CLI. To resume the deployment, run "sf deploy metadata resume". To check the status of the deployment, run "sf
-    deploy metadata report".
+  -n, --class-names=<value>...  Apex test class names to run; default is all classes.
 
-CONFIGURATION VARIABLES
-  target-org       Username or alias of the org that all commands run against by default. (sf only)
-  org-api-version  API version of your project. Default: API version of your Dev Hub org.
+    If you select --class-names, you can't specify --suite-names or --tests.
+    For multiple classes, repeat the flag for each.
+    --class-names Class1 --class-names Class2
 
-ENVIRONMENT VARIABLES
-  SF_TARGET_ORG        Username or alias of your default org. Overrides the target-org configuration variable.
-  SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
+  -s, --suite-names=<value>...  Apex test suite names to run; default is all suites.
 
-ERROR CODES
-  Succeeded (0)          The deploy succeeded.
-  Canceled (1)           The deploy was canceled.
-  Failed (1)             The deploy failed.
-  SucceededPartial (68)  The deploy partially succeeded.
-  InProgress (69)        The deploy is in progress.
-  Pending (69)           The deploy is pending.
-  Canceling (69)         The deploy is being canceled.
+    If you select --suite-names, you can't specify --class-names or --tests.
+    For multiple suites, repeat the flag for each.
+    --suite-names Suite1 --suite-names Suite2
+
+  -t, --tests=<value>...  Apex test class names or IDs and, if applicable, test methods to run; default is all tests.
+
+    If you specify --tests, you can't specify --class-names or --suite-names
+    For multiple tests, repeat the flag for each.
+    --tests Test1 --tests Test2
 ```
 
-## `sf deploy metadata cancel`
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/2.3.16/src/commands/apex/run/test.ts)_
 
-Cancel a deploy operation.
+## `sf apex tail log`
+
+Activate debug logging and display logs in the terminal.
 
 ```
 USAGE
-  $ sf deploy metadata cancel [--json] [--async | -w <value>] [-i <value>] [-r]
+  $ sf apex tail log -o <value> [--json] [--api-version <value>] [-c] [-d <value> | -s]
 
 FLAGS
-  -i, --job-id=<value>   Job ID of the deploy operation you want to cancel.
-  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
-  -w, --wait=<minutes>   Number of minutes to wait for the command to complete and display results.
-  --async                Run the command asynchronously.
+  -c, --color                Apply default colors to noteworthy log lines.
+  -d, --debug-level=<value>  Debug level to set on the DEVELOPER_LOG trace flag for your user.
+  -o, --target-org=<value>   (required) Username or alias of the target org.
+  -s, --skip-trace-flag      Skip trace flag setup. Assumes that a trace flag and debug level are fully set up.
+  --api-version=<value>      Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Cancel a deploy operation.
+  Activate debug logging and display logs in the terminal.
 
-  Use this command to cancel a deploy operation that hasn't yet completed in the org. Deploy operations include standard
-  deploys, quick deploys, deploy validations, and deploy cancellations.
+  You can also pipe the logs to a file.
 
-  Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most
-  recent deploy operation.
+ALIASES
+  $ sf force apex log tail
 
 EXAMPLES
-  Cancel a deploy operation using a job ID:
+  Activate debug logging:
 
-    $ sf deploy metadata cancel --job-id 0Af0x000017yLUFCA2
+    $ sf apex tail log
 
-  Cancel the most recent deploy operation:
+  Specify a debug level:
 
-    $ sf deploy metadata cancel --use-most-recent
+    $ sf apex tail log --debug-level MyDebugLevel
 
-FLAG DESCRIPTIONS
-  -i, --job-id=<value>  Job ID of the deploy operation you want to cancel.
+  Skip the trace flag setup and apply default colors:
 
-    These commands return a job ID if they time out or you specified the --async flag:
+    $ sf apex tail log --color --skip-trace-flag
+```
 
-    - sf deploy metadata
-    - sf deploy metadata validate
-    - sf deploy metadata quick
-    - sf deploy metadata cancel
+_See code: [@salesforce/plugin-apex](https://github.com/salesforcecli/plugin-apex/blob/2.3.16/src/commands/apex/tail/log.ts)_
 
-    The job ID is valid for 10 days from when you started the deploy operation.
+## `sf autocomplete [SHELL]`
 
-  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+display autocomplete installation instructions
 
-    For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less.
-    If your most recent deploy operations was more than 3 days ago, this flag won't find a job ID.
+```
+USAGE
+  $ sf autocomplete [SHELL] [-r]
 
-  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+ARGUMENTS
+  SHELL  (zsh|bash|powershell) Shell type
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To
-    resume watching the cancellation, run "sf deploy metadata resume". To check the status of the cancellation, run "sf
-    deploy metadata report".
+FLAGS
+  -r, --refresh-cache  Refresh cache (ignores displaying instructions)
 
-  --async  Run the command asynchronously.
+DESCRIPTION
+  display autocomplete installation instructions
 
-    The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To
-    resume watching the cancellation, run "sf deploy metadata resume". To check the status of the cancellation, run "sf
-    deploy metadata report".
+EXAMPLES
+  $ sf autocomplete
+
+  $ sf autocomplete bash
+
+  $ sf autocomplete zsh
+
+  $ sf autocomplete powershell
+
+  $ sf autocomplete --refresh-cache
 ```
 
-## `sf deploy metadata preview`
+_See code: [@oclif/plugin-autocomplete](https://github.com/oclif/plugin-autocomplete/blob/2.3.9/src/commands/autocomplete/index.ts)_
 
-Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.
+## `sf commands`
+
+list all the commands
 
 ```
 USAGE
-  $ sf deploy metadata preview [--json] [-c] [-x <value> | -d <value> | -m <value>] [-o <value>]
+  $ sf commands [--json] [-h] [--hidden] [--tree] [--columns <value> | -x] [--sort <value>] [--filter <value>]
+    [--output csv|json|yaml |  | [--csv | --no-truncate]] [--no-header | ]
 
 FLAGS
-  -c, --ignore-conflicts       Ignore conflicts and deploy local files, even if they overwrite changes in the org.
-  -d, --source-dir=<value>...  Path to the local source files to preview.
-  -m, --metadata=<value>...    Metadata component names to preview.
-  -o, --target-org=<value>     Login username or alias for the target org.
-  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to preview.
+  -h, --help         Show CLI help.
+  -x, --extended     show extra columns
+  --columns=<value>  only show provided columns (comma-separated)
+  --csv              output is csv format [alias: --output=csv]
+  --filter=<value>   filter property by partial string matching, ex: name=foo
+  --hidden           show hidden commands
+  --no-header        hide table header from output
+  --no-truncate      do not truncate output to fit screen
+  --output=<option>  output in a more machine friendly format
+                     <options: csv|json|yaml>
+  --sort=<value>     property to sort by (prepend '-' for descending)
+  --tree             show tree of commands
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.
+  list all the commands
+```
 
-  You must run this command from within a project.
+_See code: [@oclif/plugin-commands](https://github.com/oclif/plugin-commands/blob/2.2.27/src/commands/commands.ts)_
 
-  The command outputs a table that describes what will happen if you run the "sf deploy metadata" command. The table
-  lists the metadata components that will be deployed and deleted. The table also lists the current conflicts between
-  files in your local project and components in the org. Finally, the table lists the files that won't be deployed
-  because they're included in your .forceignore file.
+## `sf config get`
 
-  If your org allows source tracking, then this command considers conflicts between the org and local. Some orgs, such
-  as production orgs, never allow source tracking. Use the "--no-track-source" flag when you create a scratch or sandbox
-  org to disable source tracking.
+Get the value of a configuration variable.
 
-  To preview the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single
-  --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double
-  quotes. The same syntax applies to --manifest and --source-dir.
+```
+USAGE
+  $ sf config get [--json] [--verbose]
 
-EXAMPLES
-  NOTE: The commands to preview a deployment and actually deploy it use similar flags. We provide a few preview examples here, but see the help for "sf deploy metadata" for more examples that you can adapt for previewing.
+FLAGS
+  --verbose  Display whether the configuration variables are set locally or globally.
 
-  Preview the deployment of source files in a directory, such as force-app:
+GLOBAL FLAGS
+  --json  Format output as json.
 
-    $ sf deploy metadata preview  --source-dir force-app
+DESCRIPTION
+  Get the value of a configuration variable.
 
-  Preview the deployment of all Apex classes:
+  Run "sf config list" to see all the configuration variables you've set. Global configuration variable are always
+  displayed; local ones are displayed if you run the command in a project directory. Run "sf config set" to set a
+  configuration variable.
 
-    $ sf deploy metadata preview --metadata ApexClass
+ALIASES
+  $ sf force config get
 
-  Preview deployment of a specific Apex class:
+EXAMPLES
+  Get the value of the "target-org" configuration variable.
 
-    $ sf deploy metadata preview --metadata ApexClass:MyApexClass
+    $ sf config get target-org
 
-  Preview deployment of all components listed in a manifest:
+  Get multiple configuration variables and display whether they're set locally or globally:
 
-    $ sf deploy metadata preview --manifest path/to/package.xml
+    $ sf config get target-org api-version --verbose
 
-FLAG DESCRIPTIONS
-  -c, --ignore-conflicts  Ignore conflicts and deploy local files, even if they overwrite changes in the org.
+CONFIGURATION VARIABLES
+  org-instance-url               URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com.
+  org-api-version                API version of your project. Default: API version of your Dev Hub org.
+  target-dev-hub                 Username or alias of your default Dev Hub org. (sf only)
+  target-org                     Username or alias of the org that all commands run against by default. (sf only)
+  org-isv-debugger-sid           ISV debugger SID.
+  org-isv-debugger-url           ISV debugger URL.
+  org-custom-metadata-templates  A valid repository URL or directory for the custom org metadata templates.
+  org-max-query-limit            Maximum number of Salesforce records returned by a CLI command. Default: 10,000.
+```
 
-    This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as
-    production orgs.
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/config/get.ts)_
 
-  -d, --source-dir=<value>...  Path to the local source files to preview.
+## `sf config list`
 
-    The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder
-    (in which case the operation is applied to all metadata types in the directory and its subdirectories).
+List the configuration variables that you've previously set.
 
-    If you specify this flag, don’t specify --metadata or --manifest.
+```
+USAGE
+  $ sf config list [--json]
 
-  -o, --target-org=<value>  Login username or alias for the target org.
+GLOBAL FLAGS
+  --json  Format output as json.
 
-    Overrides your default org.
+DESCRIPTION
+  List the configuration variables that you've previously set.
 
-  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to preview.
+  Global configuration variables apply to any Salesforce DX project and are always displayed. If you run this command
+  from a project directory, local configuration variables are also displayed.
 
-    All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
+ALIASES
+  $ sf force config list
+
+EXAMPLES
+  List both global configuration variables and those local to your project:
+
+    $ sf config list
 ```
 
-## `sf deploy metadata quick`
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/config/list.ts)_
 
-Quickly deploy a validated deployment to an org.
+## `sf config set`
+
+Set one or more configuration variables, such as your default org.
 
 ```
 USAGE
-  $ sf deploy metadata quick [--json] [--async | -w <value>] [--concise | --verbose] [-i <value>] [-o <value>] [-r]
+  $ sf config set [--json] [-g]
 
 FLAGS
-  -i, --job-id=<value>      Job ID of the deployment you want to quick deploy.
-  -o, --target-org=<value>  Login username or alias for the target org.
-  -r, --use-most-recent     Use the job ID of the most recently validated deployment.
-  -w, --wait=<minutes>      Number of minutes to wait for the command to complete and display results.
-  --async                   Run the command asynchronously.
-  --concise                 Show concise output of the deploy result.
-  --verbose                 Show verbose output of the deploy result.
+  -g, --global  Set the configuration variables globally, so they can be used from any Salesforce DX project.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Quickly deploy a validated deployment to an org.
-
-  Before you run this command, first create a validated deployment with the "sf deploy metadata validate" command, which
-  returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command.
-  Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently
-  validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded.
-
-  Executing this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These
-  tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the
-  deployment to your production org take several hours and you don’t want to risk a failed deploy.
-
-  This command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org.
-  This command doesn’t attempt to merge your source with the versions in your org.
+  Set one or more configuration variables, such as your default org.
 
-EXAMPLES
-  Run a quick deploy to your default org using a job ID:
+  Use configuration variables to set CLI defaults, such as your default org or the API version you want the CLI to use.
+  For example, if you set the "target-org" configuration variable, you don't need to specify it as a "sf deploy
+  metadata" flag if you're deploying to your default org.
 
-    $ sf deploy metadata quick --job-id 0Af0x000017yLUFCA2
+  Local configuration variables apply only to your current project. Global variables, specified with the --global flag,
+  apply in any Salesforce DX project.
 
-  Asynchronously run a quick deploy of the most recently validated deployment to an org with alias "my-prod-org":
+  The resolution order if you've set a flag value in multiple ways is as follows:
 
-    $ sf deploy metadata quick --async --use-most-recent --target-org my-prod-org
+  1. Flag value specified at the command line.
+  2. Local (project-level) configuration variable.
+  3. Global configuration variable.
 
-FLAG DESCRIPTIONS
-  -i, --job-id=<value>  Job ID of the deployment you want to quick deploy.
+  Run "sf config list" to see the configuration variables you've already set and their level (local or global).
 
-    The job ID is valid for 10 days from when you started the validation.
+ALIASES
+  $ sf force config set
 
-  -o, --target-org=<value>  Login username or alias for the target org.
+EXAMPLES
+  Set the local target-org configuration variable to an org username:
 
-    Overrides your default org.
+    $ sf config set target-org=me@my.org
 
-  -r, --use-most-recent  Use the job ID of the most recently validated deployment.
+  Set the local target-org configuration variable to an alias:
 
-    For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most
-    recent deployment validation was more than 3 days ago, this flag won't find a job ID.
+    $ sf config set target-org=my-scratch-org
 
-  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+  Set the global target-org configuration variable:
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To
-    resume watching the deploy, run "sf deploy metadata resume". To check the status of the deploy, run "sf deploy
-    metadata report".
+    $ sf config set --global target-org=my-scratch-org
 
-  --async  Run the command asynchronously.
+  Set a single configuration variable without using an equal sign; this syntax doesn't work when setting multiple
+  configuration variables:
 
-    The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To
-    resume watching the deploy, run "sf deploy metadata resume". To check the status of the deploy, run "sf deploy
-    metadata report".
+    $ sf config set target-org me@my.com
 
-ERROR CODES
-  Succeeded (0)          The deploy succeeded.
-  Canceled (1)           The deploy was canceled.
-  Failed (1)             The deploy failed.
-  SucceededPartial (68)  The deploy partially succeeded.
-  InProgress (69)        The deploy is in progress.
-  Pending (69)           The deploy is pending.
-  Canceling (69)         The deploy is being canceled.
+CONFIGURATION VARIABLES
+  org-instance-url               URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com.
+  org-api-version                API version of your project. Default: API version of your Dev Hub org.
+  target-dev-hub                 Username or alias of your default Dev Hub org. (sf only)
+  target-org                     Username or alias of the org that all commands run against by default. (sf only)
+  org-isv-debugger-sid           ISV debugger SID.
+  org-isv-debugger-url           ISV debugger URL.
+  org-custom-metadata-templates  A valid repository URL or directory for the custom org metadata templates.
+  org-max-query-limit            Maximum number of Salesforce records returned by a CLI command. Default: 10,000.
 ```
 
-## `sf deploy metadata report`
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/config/set.ts)_
 
-Check the status of a deploy operation.
+## `sf config unset`
+
+Unset local or global configuration variables.
 
 ```
 USAGE
-  $ sf deploy metadata report [--json] [-i <value>] [-r]
+  $ sf config unset [--json] [-g]
 
 FLAGS
-  -i, --job-id=<value>   Job ID of the deploy operation you want to check the status of.
-  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+  -g, --global  Unset the configuration variables globally, so they can no longer be used from any Salesforce DX
+                project.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Check the status of a deploy operation.
+  Unset local or global configuration variables.
 
-  Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations.
+  Local configuration variables apply only to your current project. Global configuration variables apply in any
+  Salesforce DX project.
 
-  Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most
-  recent deploy operation.
+ALIASES
+  $ sf force config unset
 
 EXAMPLES
-  Check the status using a job ID:
-
-    $ sf deploy metadata report --job-id 0Af0x000017yLUFCA2
-
-  Check the status of the most recent deploy operation:
-
-    $ sf deploy metadata report --use-most-recent
-
-FLAG DESCRIPTIONS
-  -i, --job-id=<value>  Job ID of the deploy operation you want to check the status of.
-
-    These commands return a job ID if they time out or you specified the --async flag:
+  Unset the local "target-org" configuration variable:
 
-    - sf deploy metadata
-    - sf deploy metadata validate
-    - sf deploy metadata quick
-    - sf deploy metadata cancel
+    $ sf config unset target-org
 
-    The job ID is valid for 10 days from when you started the deploy operation.
+  Unset multiple configuration variables globally:
 
-  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+    $ sf config unset target-org api-version --global
 
-    For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less.
-    If your most recent operation was more than 3 days ago, this flag won't find a job ID.
+CONFIGURATION VARIABLES
+  org-instance-url               URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com.
+  org-api-version                API version of your project. Default: API version of your Dev Hub org.
+  target-dev-hub                 Username or alias of your default Dev Hub org. (sf only)
+  target-org                     Username or alias of the org that all commands run against by default. (sf only)
+  org-isv-debugger-sid           ISV debugger SID.
+  org-isv-debugger-url           ISV debugger URL.
+  org-custom-metadata-templates  A valid repository URL or directory for the custom org metadata templates.
+  org-max-query-limit            Maximum number of Salesforce records returned by a CLI command. Default: 10,000.
 ```
 
-## `sf deploy metadata resume`
+_See code: [@salesforce/plugin-settings](https://github.com/salesforcecli/plugin-settings/blob/1.4.31/src/commands/config/unset.ts)_
 
-Resume watching a deploy operation.
+## `sf data create record`
+
+Create and insert a record into a Salesforce or Tooling API object.
 
 ```
 USAGE
-  $ sf deploy metadata resume [--json] [--concise | --verbose] [-i <value>] [-r] [-w <value>]
+  $ sf data create record -o <value> -s <value> -v <value> [--json] [--api-version <value>] [-t]
 
 FLAGS
-  -i, --job-id=<value>   Job ID of the deploy operation you want to resume.
-  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
-  -w, --wait=<minutes>   Number of minutes to wait for the command to complete and display results.
-  --concise              Show concise output of the deploy operation result.
-  --verbose              Show verbose output of the deploy operation result.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the Salesforce or Tooling API object that you're inserting a record
+                            into.
+  -t, --use-tooling-api     Use Tooling API so you can insert a record in a Tooling API object.
+  -v, --values=<value>      (required) Values for the flags in the form <fieldName>=<value>, separate multiple pairs
+                            with spaces.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Resume watching a deploy operation.
+  Create and insert a record into a Salesforce or Tooling API object.
 
-  Use this command to resume watching a deploy operation if the original command times out or you specified the --async
-  flag. Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations. This
-  command doesn't resume the original operation itself, because the operation always continues after you've started it,
-  regardless of whether you're watching it or not.
+  You must specify a value for all required fields of the object.
 
-  Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most
-  recent deploy operation.
+  When specifying fields, use the format <fieldName>=<value>. Enclose all field-value pairs in one set of double
+  quotation marks, delimited by spaces. Enclose values that contain spaces in single quotes.
+
+  This command inserts a record into Salesforce objects by default. Use the --use-tooling-api flag to insert into a
+  Tooling API object.
+
+ALIASES
+  $ sf force data record create
 
 EXAMPLES
-  Resume watching a deploy operation using a job ID:
+  Insert a record into the Account object of your default org; only the required Name field has a value:
 
-    $ sf deploy metadata resume --job-id 0Af0x000017yLUFCA2
+    $ sf data create record --sobject Account --values "Name=Acme"
 
-  Resume watching the most recent deploy operation:
+  Insert an Account record with values for two fields, one value contains a space; the command uses the org with alias
+  "my-scratch":
 
-    $ sf deploy metadata resume --use-most-recent
+    $ sf data create record --sobject Account --values "Name='Universal Containers' Website=www.example.com" \
+      --target-org my-scratch
 
-FLAG DESCRIPTIONS
-  -i, --job-id=<value>  Job ID of the deploy operation you want to resume.
+  Insert a record into the Tooling API object TraceFlag:
 
-    These commands return a job ID if they time out or you specified the --async flag:
+    $ sf data create record --use-tooling-api --sobject TraceFlag --values "DebugLevelId=7dl170000008U36AAE \
+      StartDate=2022-12-15T00:26:04.000+0000 ExpirationDate=2022-12-15T00:56:04.000+0000 LogType=CLASS_TRACING \
+      TracedEntityId=01p17000000R6bLAAS"
+```
 
-    - sf deploy metadata
-    - sf deploy metadata validate
-    - sf deploy metadata quick
-    - sf deploy metadata cancel
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/create/record.ts)_
 
-    The job ID is valid for 10 days from when you started the deploy operation.
+## `sf data delete bulk`
 
-  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+Bulk delete records from an org using a CSV file. Uses Bulk API 2.0.
 
-    For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less.
-    If your most recent operation was more than 3 days ago, this flag won't find a job ID.
+```
+USAGE
+  $ sf data delete bulk -o <value> -f <value> -s <value> [--json] [--api-version <value>] [-w <value> | -a] [--verbose]
 
-  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+FLAGS
+  -a, --async               Run the command asynchronously.
+  -f, --file=<value>        (required) CSV file that contains the IDs of the records to delete.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the Salesforce object, either standard or custom, that you want to
+                            delete records from.
+  -w, --wait=<value>        [default: [object Object]] Number of minutes to wait for the command to complete before
+                            displaying the results.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --verbose                 Print verbose output of failed records if result is available.
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To
-    resume watching the deploy operation, run this command again. To check the status of the deploy operation, run "sf
-    deploy metadata report".
+GLOBAL FLAGS
+  --json  Format output as json.
 
-ENVIRONMENT VARIABLES
-  SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
+DESCRIPTION
+  Bulk delete records from an org using a CSV file. Uses Bulk API 2.0.
 
-ERROR CODES
-  Succeeded (0)          The deploy succeeded.
-  Canceled (1)           The deploy was canceled.
-  Failed (1)             The deploy failed.
-  SucceededPartial (68)  The deploy partially succeeded.
-  InProgress (69)        The deploy is in progress.
-  Pending (69)           The deploy is pending.
-  Canceling (69)         The deploy is being canceled.
+  The CSV file must have only one column ("Id") and then the list of record IDs you want to delete, one ID per line.
+
+  When you execute this command, it starts a job, displays the ID, and then immediately returns control of the terminal
+  to you by default. If you prefer to wait, set the --wait flag to the number of minutes; if it times out, the command
+  outputs the IDs. Use the job ID to check the status of the job with the "sf data delete resume" command.
+
+EXAMPLES
+  Bulk delete Account records from your default org using the list of IDs in the "files/delete.csv" file:
+
+    $ sf data delete bulk --sobject Account --file files/delete.csv
+
+  Bulk delete records from a custom object in an org with alias my-scratch and wait 5 minutes for the command to
+  complete:
+
+    $ sf data delete bulk --sobject MyObject__c --file files/delete.csv --wait 5 --target-org my-scratch
 ```
 
-## `sf deploy metadata validate`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/delete/bulk.ts)_
 
-Validate a metadata deployment without actually executing it.
+## `sf data delete record`
+
+Deletes a single record from a Salesforce or Tooling API object.
 
 ```
 USAGE
-  $ sf deploy metadata validate [--json] [-a <value>] [--async] [--concise | --verbose] [-x <value>] [-m <value>] [-d <value>]
-    [--single-package --metadata-dir <value>] [-o <value>] [-t <value>] [-l
-    RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests] [-w <value>]
+  $ sf data delete record -o <value> -s <value> [--json] [--api-version <value>] [-i <value>] [-w <value>] [-t]
 
 FLAGS
-  -a, --api-version=<value>    Target API version for the validation.
-  -d, --source-dir=<value>...  Path to the local source files to validate for deployment.
-  -l, --test-level=<option>    [default: RunLocalTests] Deployment Apex testing level.
-                               <options: RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests>
-  -m, --metadata=<value>...    Metadata component names to validate for deployment.
-  -o, --target-org=<value>     Login username or alias for the target org.
-  -t, --tests=<value>...       Apex tests to run when --test-level is RunSpecifiedTests.
-  -w, --wait=<minutes>         Number of minutes to wait for the command to complete and display results.
-  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to validate for deployment.
-  --async                      Run the command asynchronously.
-  --concise                    Show concise output of the validation result.
-  --metadata-dir=<value>       Root of directory or zip file of metadata formatted files to deploy.
-  --single-package             Indicates that the metadata zip file points to a directory structure for a single
-                               package.
-  --verbose                    Show verbose output of the validation result.
+  -i, --record-id=<value>   ID of the record you’re deleting.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the Salesforce or Tooling API object that you're deleting a record
+                            from.
+  -t, --use-tooling-api     Use Tooling API so you can delete a record from a Tooling API object.
+  -w, --where=<value>       List of <fieldName>=<value> pairs that identify the record you want to delete.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Validate a metadata deployment without actually executing it.
+  Deletes a single record from a Salesforce or Tooling API object.
 
-  Use this command to verify whether a deployment will succeed without actually deploying the metadata to your org. This
-  command is similar to "sf deploy metadata", except you're required to run Apex tests, and the command returns a job ID
-  rather than executing the deployment. If the validation succeeds, then you pass this job ID to the "sf deploy metadata
-  quick" command to actually deploy the metadata. This quick deploy takes less time because it skips running Apex tests.
-  The job ID is valid for 10 days from when you started the validation. Validating first is useful if the deployment to
-  your production org take several hours and you don’t want to risk a failed deploy.
+  Specify the record you want to delete with either its ID or with a list of field-value pairs that identify the record.
+  If your list of fields identifies more than one record, the delete fails; the error displays how many records were
+  found.
 
-  You must run this command from within a project.
+  When specifying field-value pairs, use the format <fieldName>=<value>. Enclose all field-value pairs in one set of
+  double quotation marks, delimited by spaces. Enclose values that contain spaces in single quotes.
 
-  This command doesn't support source-tracking. When you quick deploy with the resulting job ID, the source you deploy
-  overwrites the corresponding metadata in your org.
+  This command deletes a record from Salesforce objects by default. Use the --use-tooling-api flag to delete from a
+  Tooling API object.
 
-  To validate the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single
-  --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double
-  quotes. The same syntax applies to --manifest and --source-dir.
+ALIASES
+  $ sf force data record delete
 
 EXAMPLES
-  NOTE: These examples focus on validating large deployments. See the help for "sf deploy metadata" for examples of deploying smaller sets of metadata which you can also use to validate.
+  Delete a record from Account with the specified (truncated) ID:
 
-  Validate the deployment of all source files in a directory to the default org:
+    $ sf data delete record --sobject Account --record-id 00180XX
 
-    $ sf deploy metadata validate --source-dir path/to/source
+  Delete a record from Account whose name equals "Acme":
 
-  Asynchronously validate the deployment and run all tests in the org with alias "my-prod-org"; command immediately
-  returns the job ID:
+    $ sf data delete record --sobject Account --where "Name=Acme"
 
-    $ sf deploy metadata validate --source-dir path/to/source --async --test-level RunAllTestsInOrg --target-org \
-      my-prod-org
+  Delete a record from Account identified with two field values, one that contains a space; the command uses the org
+  with alias "my-scratch":
 
-  Validate the deployment of all components listed in a manifest:
+    $ sf data delete record --sobject Account --where "Name='Universal Containers' Phone='(123) 456-7890'" \
+      --target-org myscratch
 
-    $ sf deploy metadata validate --manifest path/to/package.xml
+  Delete a record from the Tooling API object TraceFlag with the specified (truncated) ID:
 
-FLAG DESCRIPTIONS
-  -a, --api-version=<value>  Target API version for the validation.
+    $ sf data delete record --use-tooling-api --sobject TraceFlag --record-id 7tf8c
+```
 
-    Use this flag to override the default API version with the API version of your package.xml file. The default API
-    version is the latest version supported by the CLI.
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/delete/record.ts)_
 
-  -d, --source-dir=<value>...  Path to the local source files to validate for deployment.
+## `sf data delete resume`
 
-    The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder
-    (in which case the operation is applied to all metadata types in the directory and its subdirectories).
+Resume a bulk delete job that you previously started. Uses Bulk API 2.0.
 
-    If you specify this flag, don’t specify --metadata or --manifest.
+```
+USAGE
+  $ sf data delete resume [--json] [-o <value>] [--use-most-recent | -i <value>] [--wait <value>] [--api-version
+  <value>]
 
-  -l, --test-level=RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests  Deployment Apex testing level.
+FLAGS
+  -i, --job-id=<value>      ID of the job you want to resume.
+  -o, --target-org=<value>  Org alias or username to use for the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --use-most-recent         Use the ID of the most recently-run bulk job.
+  --wait=<value>            [default: [object Object]] Number of minutes to wait for the command to complete before
+                            displaying the results.
 
-    Valid values are:
-
-    - RunSpecifiedTests — Runs only the tests that you specify with the --run-tests flag. Code coverage requirements
-    differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of
-    75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
-    trigger individually and is different than the overall coverage percentage.
-
-    - RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked
-    packages. This test level is the default for production deployments that include Apex classes or triggers.
-
-    - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
-
-    If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more
-    information, see [Running Tests in a
-    Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)
-    in the "Metadata API Developer Guide".
-
-  -o, --target-org=<value>  Login username or alias for the target org.
-
-    Overrides your default org.
-
-  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
-
-    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
-    returns the job ID. To resume watching the validation, run "sf deploy metadata resume". To check the status of the
-    validation, run "sf deploy metadata report".
-
-  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to validate for deployment.
-
-    All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
-
-  --async  Run the command asynchronously.
-
-    The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the
-    CLI. To resume watching the validation, run "sf deploy metadata resume". To check the status of the validation, run
-    "sf deploy metadata report".
+GLOBAL FLAGS
+  --json  Format output as json.
 
-CONFIGURATION VARIABLES
-  target-org       Username or alias of the org that all commands run against by default. (sf only)
-  org-api-version  API version of your project. Default: API version of your Dev Hub org.
+DESCRIPTION
+  Resume a bulk delete job that you previously started. Uses Bulk API 2.0.
 
-ENVIRONMENT VARIABLES
-  SF_TARGET_ORG        Username or alias of your default org. Overrides the target-org configuration variable.
-  SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
+  The command uses the job ID returned by the "sf data delete bulk" command or the most recently-run bulk delete job.
 
-ERROR CODES
-  Succeeded (0)          The deploy succeeded.
-  Canceled (1)           The deploy was canceled.
-  Failed (1)             The deploy failed.
-  SucceededPartial (68)  The deploy partially succeeded.
-  InProgress (69)        The deploy is in progress.
-  Pending (69)           The deploy is pending.
-  Canceling (69)         The deploy is being canceled.
-```
+EXAMPLES
+  Resume a bulk delete job from your default org using an ID:
 
-## `sf env compute collaborator add`
+    $ sf data delete resume --job-id 750xx000000005sAAA
 
-Add a Heroku user as a collaborator on this Functions account, allowing them to attach Heroku add-ons to compute environments.
+  Resume the most recently run bulk delete job for an org with alias my-scratch:
 
+    $ sf data delete resume --use-most-recent --target-org my-scratch
 ```
-USAGE
-  $ sf env compute collaborator add -h <value>
-
-FLAGS
-  -h, --heroku-user=<value>  (required) Email address of the Heroku user you're adding as a collaborator.
-
-EXAMPLES
-  Add a Heroku user as a collaborator on this Functions account.
 
-    $ sf env compute collaborator add --heroku-user example@heroku.com
-```
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/delete/resume.ts)_
 
-## `sf env create compute`
+## `sf data export tree`
 
-Create a compute environment for use with Salesforce Functions.
+Export data from an org into one or more JSON files.
 
 ```
 USAGE
-  $ sf env create compute [--json] [-o <value>] [-a <value>]
+  $ sf data export tree -o <value> -q <value> [--json] [--api-version <value>] [-p] [-x <value>] [-d <value>]
 
 FLAGS
-  -a, --alias=<value>          Alias for the created environment.
-  -o, --connected-org=<value>  Username or alias for the org that the compute environment should be connected to.
+  -d, --output-dir=<value>  Directory in which to generate the JSON files; default is current directory.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -p, --plan                Generate multiple sObject tree files and a plan definition file for aggregated import.
+  -q, --query=<value>       (required) SOQL query, or filepath of a file that contains the query, to retrieve records.
+  -x, --prefix=<value>      Prefix of generated files.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Create a compute environment for use with Salesforce Functions.
+  Export data from an org into one or more JSON files.
 
-  Compute environments must be connected to a Salesforce org. By default the command uses your local environment's
-  connected org. Use the '--connected-org' flag to specify a specific org. Run 'sf env list' to see a list of
-  environments.
+  Specify a SOQL query, either directly at the command line or read from a file, to retrieve the data you want to
+  export. The exported data is written to JSON files in sObject tree format, which is a collection of nested,
+  parent-child records with a single root record. Use these JSON files to import data into an org with the "sf data
+  import tree" command.
+
+  If your SOQL query references multiple objects, the command generates a single JSON file by default. You can specify
+  the --plan flag to generate separate JSON files for each object and a plan definition file that aggregates them. You
+  then specify just this plan definition file when you import the data into an org.
+
+  The SOQL query can return a maximum of 2,000 records. For more information, see the REST API Developer Guide.
+  (https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobject_tree.htm).
+
+ALIASES
+  $ sf force data tree export
 
 EXAMPLES
-  Create a compute environment to run Salesforce Functions:
+  Export records retrieved with the specified SOQL query into a single JSON file in the current directory; the command
+  uses your default org:
 
-    $ sf env create compute
+    $ sf data export tree --query "SELECT Id, Name, (SELECT Name, Address__c FROM Properties__r) FROM Broker__c"
 
-  Connect the environment to a specific org:
+  Export data using a SOQL query in the "query.txt" file and generate JSON files for each object and a plan that
+  aggregates them:
 
-    $ sf env create compute --connected-org=org-alias
+    $ sf data export tree --query query.txt --plan
 
-  Create an alias for the compute environment:
+  Prepend "export-demo" before each generated file and generate the files in the "export-out" directory; run the
+  command on the org with alias "my-scratch":
 
-    $ sf env create compute --alias environment-alias
+    $ sf data export tree --query query.txt --plan --prefix export-demo --output-dir export-out --target-org \
+      my-scratch
 ```
 
-## `sf env create sandbox`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/export/tree.ts)_
 
-Create a sandbox org.
+## `sf data get record`
+
+Retrieve and display a single record of a Salesforce or Tooling API object.
 
 ```
 USAGE
-  $ sf env create sandbox [--json] [-f <value> | -n <value> | -l Developer|Developer_Pro|Partial|Full] [-s] [-a <value>]
-    [-w <value> | --async] [-i <value> | ] [-c <value> | ] [-o <value>] [--no-prompt] [--no-track-source]
+  $ sf data get record -o <value> -s <value> [--json] [--api-version <value>] [-i <value>] [-w <value>] [-t]
 
 FLAGS
-  -a, --alias=<value>                                        Alias for the sandbox org.
-  -c, --clone=<value>                                        Name of the sandbox org to clone.
-  -f, --definition-file=<value>                              Path to a sandbox definition file.
-  -i, --poll-interval=<seconds>                              Number of seconds to wait between retries.
-  -l, --license-type=(Developer|Developer_Pro|Partial|Full)  [default: Developer] Type of sandbox license.
-  -n, --name=<value>                                         Name of the sandbox org.
-  -o, --target-org=<value>                                   Username or alias of the production org that contains the
-                                                             sandbox license.
-  -s, --set-default                                          Set the sandbox org as your default org.
-  -w, --wait=<minutes>                                       Number of minutes to wait for the sandbox org to be ready.
-  --async                                                    Request the sandbox creation, but don't wait for it to
-                                                             complete.
-  --no-prompt                                                Don't prompt for confirmation about the sandbox
-                                                             configuration.
-  --no-track-source                                          Do not use source tracking for this sandbox.
+  -i, --record-id=<value>   ID of the record you’re retrieving.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the Salesforce or Tooling API object that you're retrieving a record
+                            from.
+  -t, --use-tooling-api     Use Tooling API so you can retrieve a record from a Tooling API object.
+  -w, --where=<value>       List of <fieldName>=<value> pairs that identify the record you want to display.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Create a sandbox org.
+  Retrieve and display a single record of a Salesforce or Tooling API object.
 
-  There are two ways to create a sandbox org: specify a definition file that contains the sandbox options or use the
-  --name and --license-type flags to specify the two required options. If you want to set an option other than name or
-  license type, such as apexClassId, you must use a definition file.
+  Specify the record you want to retrieve with either its ID or with a list of field-value pairs that identify the
+  record. If your list of fields identifies more than one record, the command fails; the error displays how many records
+  were found.
+
+  When specifying field-value pairs, use the format <fieldName>=<value>. Enclose all field-value pairs in one set of
+  double quotation marks, delimited by spaces. Enclose values that contain spaces in single quotes.
+
+  The command displays all the record's fields and their values, one field per terminal line. Fields with no values are
+  displayed as "null".
+
+  This command retrieves a record from Salesforce objects by default. Use the --use-tooling-api flag to retrieve from a
+  Tooling API object.
+
+ALIASES
+  $ sf force data record get
 
 EXAMPLES
-  Create a sandbox org using a definition file and give it the alias "MyDevSandbox". The production org that contains
-  the sandbox license has the alias "prodOrg".
+  Retrieve and display a record from Account with the specified (truncated) ID:
 
-    $ sf env create sandbox -f config/dev-sandbox-def.json --alias MyDevSandbox --target-org prodOrg
+    $ sf data get record --sobject Account --record-id 00180XX
 
-  Create a sandbox org by directly specifying its name and type of license (Developer) instead of using a definition
-  file. Set the sandbox org as your default.
+  Retrieve a record from Account whose name equals "Acme":
 
-    $ sf env create sandbox --name mysandbox --license-type Developer --alias MyDevSandbox --target-org prodOrg \
-      --set-default
+    $ sf data get record --sobject Account --where "Name=Acme"
 
-FLAG DESCRIPTIONS
-  -a, --alias=<value>  Alias for the sandbox org.
+  Retrieve a record from Account identified with two field values, one that contains a space; the command uses the org
+  with alias "my-scratch":
 
-    When you create a sandbox, the generated usernames are based on the usernames present in the production org. To
-    ensure uniqueness, the new usernames are appended with the name of the sandbox. For example, the username
-    "user@example.com" in the production org results in the username "user@example.com.mysandbox" in a sandbox named
-    "mysandbox". When you set an alias for a sandbox org, it's assigned to the resulting username of the user running
-    this command.
+    $ sf data get record --sobject Account --where "Name='Universal Containers' Phone='(123) 456-7890'" --target-org \
+      myscratch
 
-  -c, --clone=<value>  Name of the sandbox org to clone.
+  Retrieve a record from the Tooling API object TraceFlag with the specified (truncated) ID:
 
-    The value of clone must be an existing sandbox in the same target-org.
+    $ sf data get record --use-tooling-api --sobject TraceFlag --record-id 7tf8c
+```
 
-  -f, --definition-file=<value>  Path to a sandbox definition file.
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/get/record.ts)_
 
-    The sandbox definition file is a blueprint for the sandbox. You can create different definition files for each
-    sandbox type that you use in the development process. See
-    <https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_sandbox_definition.htm> for all
-    the options you can specify in the defintion file.
+## `sf data import tree`
 
-  -n, --name=<value>  Name of the sandbox org.
+Import data from one or more JSON files into an org.
 
-    The name must be a unique alphanumeric string (10 or fewer characters) to identify the sandbox. You can’t reuse a
-    name while a sandbox is in the process of being deleted.
+```
+USAGE
+  $ sf data import tree -o <value> [--json] [--api-version <value>] [-f <value> | -p <value>] [--config-help]
 
-  -o, --target-org=<value>  Username or alias of the production org that contains the sandbox license.
+FLAGS
+  -f, --files=<value>...    Comma-separated and in-order JSON files that contain the records, in sObject tree format,
+                            that you want to insert.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -p, --plan=<value>        Plan definition file to insert multiple data files.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --config-help             Display schema information for the --plan configuration file to stdout; if you specify this
+                            flag, all other flags except --json are ignored.
 
-    When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to
-    the new sandbox org.
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -w, --wait=<minutes>  Number of minutes to wait for the sandbox org to be ready.
+DESCRIPTION
+  Import data from one or more JSON files into an org.
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays
-    the "sf env resume sandbox" command you run to check the status of the create. The displayed command includes the
-    job ID for the running sandbox creation.
+  The JSON files that contain the data are in sObject tree format, which is a collection of nested, parent-child records
+  with a single root record. Use the "sf data export tree" command to generate these JSON files.
 
-  --async  Request the sandbox creation, but don't wait for it to complete.
+  If you used the --plan flag when exporting the data to generate a plan definition file, use the --plan flag to
+  reference the file when you import. If you're not using a plan, use the --files flag to list the files. If you specify
+  multiple JSON files that depend on each other in a parent-child relationship, be sure you list them in the correct
+  order.
 
-    The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue
-    to use the CLI. To check the status of the sandbox creation, run "sf env resume sandbox".
+  The sObject Tree API supports requests that contain up to 200 records. For more information, see the REST API
+  Developer Guide.
+  (https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobject_tree.htm)
 
-  --no-track-source  Do not use source tracking for this sandbox.
+ALIASES
+  $ sf force data tree import
 
-    We recommend you enable source tracking in Developer and Developer Pro sandbox, which is why it's the default
-    behavior. Source tracking allows you to track the changes you make to your metadata, both in your local project and
-    in the sandbox, and to detect any conflicts between the two.
+EXAMPLES
+  Import the records contained in two JSON files into the org with alias "my-scratch":
 
-    To disable source tracking in the new sandbox, specify the --no-track-source flag. The main reason to disable source
-    tracking is for performance. For example, while you probably want to deploy metadata and run Apex tests in your
-    CI/CD jobs, you probably don't want to incur the costs of source tracking (checking for conflicts, polling the
-    SourceMember object, various file system operations.) This is a good use case for disabling source tracking in the
-    sandbox.
+    $ sf data import tree --files Contact.json,Account.json --target-org my-scratch
+
+  Import records using a plan definition file into your default org:
+
+    $ sf data import tree --plan Account-Contact-plan.json
 ```
 
-## `sf env create scratch`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/import/tree.ts)_
 
-Create a scratch org.
+## `sf data query`
+
+Execute a SOQL query.
 
 ```
 USAGE
-  $ sf env create scratch [--json] [-a <value>] [--async] [-d] [-f <value>] [-v <value>] [-c] [-e
-    developer|enterprise|group|professional|partner-developer|partner-enterprise|partner-group|partner-professional]
-    [-m] [-y <value>] [-w <value>] [--api-version <value>] [-i <value>] [-t]
+  $ sf data query -o <value> [--json] [--api-version <value>] [-q <value>] [-f <value>] [-w <value> [-b | -t]]
+    [--async ] [--all-rows] [-r human|json|csv]
 
 FLAGS
-  -a, --alias=<value>            Alias for the scratch org.
-  -d, --set-default              Set the scratch org as your default org
-  -e, --edition=<option>         Salesforce edition of the scratch org.
-                                 <options: developer|enterprise|group|professional|partner-developer|partner-enterprise|
-                                 partner-group|partner-professional>
-  -f, --definition-file=<value>  Path to a scratch org definition file.
-  -i, --client-id=<value>        Consumer key of the Dev Hub connected app.
-  -t, --[no-]track-source        Use source tracking for this scratch org. Set --no-track-source to disable source
-                                 tracking.
-  -v, --target-dev-hub=<value>   Username or alias of the Dev Hub org.
-  -w, --wait=<minutes>           Number of minutes to wait for the scratch org to be ready.
-  -y, --duration-days=<days>     Number of days before the org expires.
-  --api-version=<value>          Override the api version used for api requests made by this command
-  --async                        Request the org, but don't wait for it to complete.
-
-PACKAGING FLAGS
-  -c, --no-ancestors  Don't include second-generation managed package (2GP) ancestors in the scratch org.
-  -m, --no-namespace  Create the scratch org with no namespace, even if the Dev Hub has a namespace.
+  -b, --bulk                    Use Bulk API 2.0 to run the query.
+  -f, --file=<value>            File that contains the SOQL query.
+  -o, --target-org=<value>      (required) Username or alias of the target org.
+  -q, --query=<value>           SOQL query to execute.
+  -r, --result-format=<option>  [default: human] Format to display the results; the --json flag overrides this flag.
+                                <options: human|json|csv>
+  -t, --use-tooling-api         Use Tooling API so you can run queries on Tooling API objects.
+  -w, --wait=<value>            Time to wait for the command to finish, in minutes.
+  --all-rows                    Include deleted records. By default, deleted records are not returned.
+  --api-version=<value>         Override the api version used for api requests made by this command
+  --async                       Use Bulk API 2.0, but don't wait for the job to complete.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Create a scratch org.
+  Execute a SOQL query.
 
-  There are two ways to create a scratch org: specify a definition file that contains the options or use the --edition
-  flag to specify the one required option. If you want to set options other than the edition, such as org features or
-  settings, you must use a definition file.
+  Specify the SOQL query at the command line with the --query flag or read the query from a file with the --file flag.
 
-  You must specify a Dev Hub to create a scratch org, either with the --target-dev-hub flag or by setting your default
-  Dev Hub with the target-dev-hub configuration variable.
+  If your query returns more than 10,000 records, specify the --bulk flag. The command then runs the query using Bulk
+  API 2.0, which has higher limits than the default API used by the command.
 
-EXAMPLES
-  Create a Developer edition scratch org using your default Dev Hub and give the scratch org an alias:
+  When using --bulk, the command waits 3 minutes by default for the query to complete. Use the --wait parameter to
+  specify a different number of minutes to wait, or set --wait to 0 to immediately return control to the terminal. If
+  you set --wait to 0, or you use the --async flag, or the command simply times out, the command displays an ID. Pass
+  this ID to the the "data query resume" command using the --bulk-query-id flag to get the results; pass the ID to the
+  "data resume" command to get the job status.
 
-    $ sf env create scratch --edition=developer --alias my-scratch-org
+ALIASES
+  $ sf force data soql query
 
-  Specify the Dev Hub using its alias and a scratch org definition file. Set the scratch org as your default and
-  specify that it expires in 3 days:
+EXAMPLES
+  Specify a SOQL query at the command line; the command uses your default org:
 
-    $ sf env create scratch --target-dev-hub=MyHub --definition-file config/project-scratch-def.json --set-default \
-      --duration-days 3
+    $ sf data query --query "SELECT Id, Name, Account.Name FROM Contact"
 
-FLAG DESCRIPTIONS
-  -a, --alias=<value>  Alias for the scratch org.
+  Read the SOQL query from a file called "query.txt"; the command uses the org with alias "my-scratch":
 
-    New scratch orgs include one administrator by default. The admin user's username is auto-generated and looks
-    something like test-wvkpnfm5z113@example.com. When you set an alias for a new scratch org, it's assigned this
-    username.
+    $ sf data query --file query.txt --target-org my-scratch
 
-  -e, --edition=developer|enterprise|group|professional|partner-developer|partner-enterprise|partner-group|partner-professional
+  Use Tooling API to run a query on the ApexTrigger Tooling API object:
 
-    Salesforce edition of the scratch org.
+    $ sf data query --query "SELECT Name FROM ApexTrigger" --use-tooling-api
 
-    The editions that begin with "partner-" are available only if the Dev Hub org is a Partner Business Org.
+  Use Bulk API 2.0 to run a query that returns many rows, and return control to the terminal immediately:
 
-  -f, --definition-file=<value>  Path to a scratch org definition file.
+    $ sf data query --query "SELECT Id FROM Contact" --bulk --wait 0
+```
 
-    The scratch org definition file is a blueprint for the scratch org. It mimics the shape of an org that you use in
-    the development life cycle, such as acceptance testing, packaging, or production. See
-    <https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm> for
-    all the option you can specify in the definition file.
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/query.ts)_
 
-  -t, --[no-]track-source  Use source tracking for this scratch org. Set --no-track-source to disable source tracking.
+## `sf data query resume`
 
-    We recommend you enable source tracking in scratch orgs, which is why it's the default behavior. Source tracking
-    allows you to track the changes you make to your metadata, both in your local project and in the scratch org, and to
-    detect any conflicts between the two.
+View the status of a bulk query.
 
-    To disable source tracking in the new scratch org, specify the --no-track-source flag. The main reason to disable
-    source tracking is for performance. For example, while you probably want to deploy metadata and run Apex tests in
-    your CI/CD jobs, you probably don't want to incur the costs of source tracking (checking for conflicts, polling the
-    SourceMember object, various file system operations.) This is a good use case for disabling source tracking in the
-    scratch org.
+```
+USAGE
+  $ sf data query resume [--json] [-o <value>] [--api-version <value>] [-r human|json|csv] [--use-most-recent | -i
+    <value>]
 
-  -v, --target-dev-hub=<value>  Username or alias of the Dev Hub org.
+FLAGS
+  -i, --bulk-query-id=<value>   Job ID of the bulk query.
+  -o, --target-org=<value>      Org alias or username to use for the target org.
+  -r, --result-format=<option>  [default: human] Format to display the results; the --json flag overrides this flag.
+                                <options: human|json|csv>
+  --api-version=<value>         Override the api version used for api requests made by this command
+  --use-most-recent             Use the most recent bulk query ID from cache.
 
-    Overrides the value of the target-dev-hub configuration variable, if set.
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -w, --wait=<minutes>  Number of minutes to wait for the scratch org to be ready.
+DESCRIPTION
+  View the status of a bulk query.
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays
-    the job ID. To resume the scratch org creation, run the env resume scratch command and pass it the job ID.
+  Run this command using the job ID returned from the "sf data query --bulk" command.
 
-  --async  Request the org, but don't wait for it to complete.
+ALIASES
+  $ sf force data soql bulk report
 
-    The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue
-    to use the CLI. To resume the scratch org creation, run "sf env resume scratch".
+EXAMPLES
+  View the status of a bulk query with the specified ID:
+
+    $ sf data query resume --bulk-query-id 7500x000005BdFzXXX
 ```
 
-## `sf env delete`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/query/resume.ts)_
+
+## `sf data resume`
 
-Delete an environment.
+View the status of a bulk data load job or batch.
 
 ```
 USAGE
-  $ sf env delete [--json] [-e <value> | ] [--confirm <value>]
+  $ sf data resume -o <value> -i <value> [--json] [--api-version <value>] [-b <value>]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
-  --confirm=name...             Confirmation name.
+  -b, --batch-id=<value>    ID of the batch whose status you want to view; you must also specify the job ID.
+  -i, --job-id=<value>      (required) ID of the job whose status you want to view.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Delete an environment.
+  View the status of a bulk data load job or batch.
 
-  You must include the name of the environment to delete using '--target-compute'. Run 'sf env list' to see a list of
-  environments.
-
-  Running this command will prompt a confirmation. If you want to skip this confirmation, use the '--confirm' flag and
-  the environment alias to skip confirmation.
+  Run this command using the job ID or batch ID returned from the "sf data delete bulk" or "sf data upsert bulk"
+  commands.
 
 EXAMPLES
-  Delete a compute environment:
+  View the status of a bulk load job:
 
-    $ sf env delete --target-compute environment-alias
+    $ sf data resume --job-id 750xx000000005sAAA
 
-  Delete without a confirmation step:
+  View the status of a bulk load job and a specific batches:
 
-    $ sf env delete --target-compute environment-alias --confirm environment-alias
+    $ sf data resume --job-id 750xx000000005sAAA --batch-id 751xx000000005nAAA
 ```
 
-## `sf env delete sandbox`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/resume.ts)_
 
-Delete a sandbox.
+## `sf data update record`
+
+Updates a single record of a Salesforce or Tooling API object.
 
 ```
 USAGE
-  $ sf env delete sandbox [--json] [-o <value>] [-p]
+  $ sf data update record -o <value> -s <value> -v <value> [--json] [--api-version <value>] [-i <value>] [-w <value>]
+    [-t]
 
 FLAGS
-  -o, --target-org=<value>  Sandbox alias or login user.
-  -p, --no-prompt           Don't prompt the user to confirm the deletion.
+  -i, --record-id=<value>   ID of the record you’re updating.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the Salesforce or Tooling API object that contains the record you're
+                            updating.
+  -t, --use-tooling-api     Use Tooling API so you can update a record in a Tooling API object.
+  -v, --values=<value>      (required) Fields that you're updating, in the format of <fieldName>=<value> pairs.
+  -w, --where=<value>       List of <fieldName>=<value> pairs that identify the record you want to update.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Delete a sandbox.
+  Updates a single record of a Salesforce or Tooling API object.
+
+  Specify the record you want to update with either its ID or with a list of field-value pairs that identify the record.
+  If your list of fields identifies more than one record, the delete fails; the error displays how many records were
+  found.
 
-  Specify a sandbox with either the username you used when you logged into it with "sf login", or the alias you gave the
-  sandbox when you created it. Run "sf env list" to view all your environments, including sandboxes, and their aliases.
+  When using field-value pairs for both identifying the record and specifiyng the new field values, use the format
+  <fieldName>=<value>. Enclose all field-value pairs in one set of double quotation marks, delimited by spaces. Enclose
+  values that contain spaces in single quotes.
+
+  This command updates a record in Salesforce objects by default. Use the --use-tooling-api flag to update a Tooling API
+  object.
+
+ALIASES
+  $ sf force data record update
 
 EXAMPLES
-  Delete a sandbox with alias my-sandbox:
+  Update the Name field of an Account record with the specified (truncated) ID:
 
-    $ sf env delete sandbox --target-org=my-sandbox
+    $ sf data update record --sobject Account --record-id 001D0 --values "Name=NewAcme"
 
-  Specify a username instead of an alias:
+  Update the Name field of an Account record whose current name is 'Old Acme':
 
-    $ sf env delete sandbox --target-org=myusername@example.com.qa
+    $ sf data update record --sobject Account --where "Name='Old Acme'" --values "Name='New Acme'"
 
-  Delete the sandbox without prompting to confirm :
+  Update the Name and Website fields of an Account record with the specified (truncated) ID:
+
+    $ sf data update record --sobject Account --record-id 001D0 --values "Name='Acme III' Website=www.example.com"
+
+  Update the ExpirationDate field of a record of the Tooling API object TraceFlag using the specified (truncated) ID:
 
-    $ sf env delete sandbox --target-org=my-sandbox --no-prompt
+    $ sf data update record -t --sobject TraceFlag --record-id 7tf170000009cUBAAY --values \
+      "ExpirationDate=2017-12-01T00:58:04.000+0000"
 ```
 
-## `sf env delete scratch`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/update/record.ts)_
 
-Delete a scratch org.
+## `sf data upsert bulk`
+
+Bulk upsert records to an org from a CSV file. Uses Bulk API 2.0.
 
 ```
 USAGE
-  $ sf env delete scratch [--json] [-o <value>] [-p]
+  $ sf data upsert bulk -o <value> -f <value> -s <value> -i <value> [--json] [--api-version <value>] [-w <value> | -a]
+    [--verbose]
 
 FLAGS
-  -o, --target-org=<value>  Scratch org alias or login user.
-  -p, --no-prompt           Don't prompt the user to confirm the deletion.
+  -a, --async                Run the command asynchronously.
+  -f, --file=<value>         (required) CSV file that contains the IDs of the records to delete.
+  -i, --external-id=<value>  (required) Name of the external ID field, or the Id field.
+  -o, --target-org=<value>   (required) Username or alias of the target org.
+  -s, --sobject=<value>      (required) API name of the Salesforce object, either standard or custom, that you want to
+                             delete records from.
+  -w, --wait=<value>         [default: [object Object]] Number of minutes to wait for the command to complete before
+                             displaying the results.
+  --api-version=<value>      Override the api version used for api requests made by this command
+  --verbose                  Print verbose output of failed records if result is available.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Delete a scratch org.
+  Bulk upsert records to an org from a CSV file. Uses Bulk API 2.0.
 
-  Specify a scratch org with either the username you used when you logged into it with "sf login", or the alias you gave
-  the scratch org when you created it. Run "sf env list" to view all your environments, including scratch orgs, and
-  their aliases.
+  An upsert refers to inserting a record into a Salesforce object if the record doesn't already exist, or updating it if
+  it does exist.
 
-EXAMPLES
-  Delete a scratch org with alias my-scratch-org:
+  When you execute this command, it starts a job, displays the ID, and then immediately returns control of the terminal
+  to you by default. If you prefer to wait, set the --wait flag to the number of minutes; if it times out, the command
+  outputs the IDs. Use the job and batch IDs to check the status of the job with the "sf data upsert resume" command.
 
-    $ sf env delete scratch --target-org=my-scratch-org
+  See "Prepare CSV Files" in the Bulk API Developer Guide for details on formatting your CSV file.
+  (https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/datafiles_prepare_csv.htm)
 
-  Specify a username instead of an alias:
+EXAMPLES
+  Bulk upsert records to the Contact object in your default org:
 
-    $ sf env delete scratch --target-org=test-123456-abcdefg@example.com
+    $ sf data upsert bulk --sobject Contact --file files/contacts.csv --external-id Id
 
-  Delete the scratch org without prompting to confirm :
+  Bulk upsert records to a custom object in an org with alias my-scratch and wait 5 minutes for the command to
+  complete:
 
-    $ sf env delete scratch --target-org=my-scratch-org --no-prompt
+    $ sf data upsert bulk --sobject MyObject__c --file files/file.csv --external-id MyField__c --wait 5 --target-org \
+      my-scratch
 ```
 
-## `sf env display`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/upsert/bulk.ts)_
+
+## `sf data upsert resume`
 
-Display details about an environment.
+Resume a bulk upsert job that you previously started. Uses Bulk API 2.0.
 
 ```
 USAGE
-  $ sf env display [--json] [-e <value>]
+  $ sf data upsert resume [--json] [-o <value>] [--use-most-recent | -i <value>] [--wait <value>] [--api-version
+  <value>]
 
 FLAGS
-  -e, --target-env=<value>  Environment alias or login user.
+  -i, --job-id=<value>      ID of the job you want to resume.
+  -o, --target-org=<value>  Org alias or username to use for the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --use-most-recent         Use the ID of the most recently-run bulk job.
+  --wait=<value>            [default: [object Object]] Number of minutes to wait for the command to complete before
+                            displaying the results.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Display details about an environment.
+  Resume a bulk upsert job that you previously started. Uses Bulk API 2.0.
 
-  Specify an environment with either the username you used when you logged into the environment with "sf login", or the
-  alias you gave the environment when you created it. Run "sf env list" to view all your environments and their aliases.
-
-  Output depends on the type of environment. For example, scratch org details include the access token, alias, username
-  of the associated Dev Hub, the creation and expiration date, the generated scratch org username, and more. Compute
-  environment details include the alias, connected orgs, creation date, project name, and more.
+  The command uses the job ID returned from the "sf data upsert bulk" command or the most recently-run bulk upsert job.
 
 EXAMPLES
-  Display details about a scratch org with alias my-scratch-org:
-
-    $ sf env display --target-env=my-scratch-org
+  Resume a bulk upsert job from your default org using an ID:
 
-  Specify a username instead of an alias:
-
-    $ sf env display --target-env=test-123456-abcdefg@example.com
+    $ sf data upsert resume --job-id 750xx000000005sAAA
 
-  Specify JSON format and redirect output into a file:
+  Resume the most recently run bulk upsert job for an org with alias my-scratch:
 
-    $ sf env display --target-env=my-scratch-org --json > tmp/MyOrdDesc.json
+    $ sf data upsert resume --use-most-recent --target-org my-scratch
 ```
 
-## `sf env list`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/data/upsert/resume.ts)_
 
-List the environments you’ve created or logged into.
+## `sf doctor`
+
+Gather CLI configuration data and run diagnostic tests to discover and report potential problems in your environment.
 
 ```
 USAGE
-  $ sf env list [--json] [-a] [--columns <value>] [--csv] [--filter <value>] [--no-header] [--no-truncate]
-    [--output csv|json|yaml] [--sort <value>]
+  $ sf doctor [--json] [-c <value>] [-p <value>] [-d <value>] [-i]
 
 FLAGS
-  -a, --all             Show all environments, even inactive ones.
-  --columns=<value>...  List of columns to display.
-  --csv                 Output in csv format [alias: --output=csv]
-  --filter=<value>      Filter property by partial string matching.
-  --no-header           Hide table header from output.
-  --no-truncate         Don't truncate output to fit screen.
-  --output=<option>     Format in which to display the output.
-                        <options: csv|json|yaml>
-  --sort=<value>        Column to sort by (prepend '-' for descending).
+  -c, --command=<value>     Command to run in debug mode; results are written to a log file.
+  -d, --output-dir=<value>  Directory to save all created files rather than the current working directory.
+  -i, --create-issue        Create a new issue on our GitHub repo and attach all diagnostic results.
+  -p, --plugin=<value>      Specific plugin on which to run diagnostics.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List the environments you’ve created or logged into.
-
-  By default, the command displays active environments. For orgs, active means unexpired scratch orgs and orgs you’re
-  currently logged into.
+  Gather CLI configuration data and run diagnostic tests to discover and report potential problems in your environment.
 
-  Output is displayed in multiple tables, one for each environment type. For example, the Salesforce Orgs table lists
-  the non-scratch orgs you’re logged into, such as sandboxes, Dev Hubs, production orgs, and so on. Scratch orgs and
-  compute environments get their own tables.
+  When you run the doctor command without parameters, it first displays a diagnostic overview of your environment. It
+  then writes a detailed diagnosis to a JSON file in the current directory. Use the --outputdir to specify a different
+  directory. To run diagnostic tests on a specific plugin, use the --plugin parameter. If the plugin isn't listening to
+  the doctor, then you get a warning.
 
-  The two org tables show similar information, such as aliases, information about the org, and how you authorized
-  (logged into) it, such as with a web browser or JWT. The scratch org table also shows the expiration date. For
-  non-scratch orgs, the Username column refers to the user you logged into the org with. For scratch orgs it refers to
-  the username that was generated for you when you created the scratch org. Your default scratch org or Dev Hub org is
-  indicated with the "target-org" or "target-dev-hub" configuration variable, respectively, in the Config column.
+  Use the --command parameter to run a specific command in debug mode; the doctor writes both stdout and stderr to
+  \*.log files that you can provide to Salesforce Customer Support or attach to a GitHub issue.
 
-  The compute environment table shows the alias, information about the connected orgs, the project name, and more.
-
-  Use the table manipulation flags, such as --filter and --sort, to change how the data is displayed.
-
-  Run "sf env display" to view details about a specific environment.
+  Plugin providers can also implement their own doctor diagnostic tests by listening to the "sf-doctor" event and
+  running plugin specific tests that are then included in the doctor diagnostics log.
 
 EXAMPLES
-  List all active environments:
-
-    $ sf env list
-
-  List both active and inactive environments:
-
-    $ sf env list --all
-
-  Filter the output to list only orgs you authorized using a web browser; "Auth Method" is the name of a column:
-
-    $ sf env list --filter "Auth Method=web"
-
-  Display only the Aliases column and sort the aliases in descending order:
+  Run CLI doctor diagnostics:
 
-    $ sf env list --sort "-Aliases" --columns "Aliases"
+    $ sf doctor
 
-  Don't truncate the displayed output and instead wrap text that's wider than your terminal:
+  Run CLI doctor diagnostics and the specified command, and write the debug output to a file:
 
-    $ sf env list --no-truncate
+    $ sf doctor --command "force:org:list --all"
 
-  Display only the table data, not the headers, in comma-separated value (csv) format:
+  Run CLI doctor diagnostics for a specific plugin:
 
-    $ sf env list --csv --no-header
+    $ sf doctor --plugin @salesforce/plugin-source
 ```
 
-## `sf env log`
+_See code: [@salesforce/plugin-info](https://github.com/salesforcecli/plugin-info/blob/2.6.46/src/commands/doctor.ts)_
 
-Stream log output for an environment.
+## `sf force data bulk delete`
+
+Bulk delete records from an org using a CSV file. Uses Bulk API 1.0.
 
 ```
 USAGE
-  $ sf env log [-e <value> | ] [-n <value>]
+  $ sf force data bulk delete -o <value> -f <value> -s <value> [--json] [--api-version <value>] [-w <value>]
 
 FLAGS
-  -e, --target-compute=<value>  Compute environment name to retrieve logs.
-  -n, --num=<value>             Number of lines to display.
+  -f, --file=<value>        (required) CSV file that contains the IDs of the records to delete.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the Salesforce object, either standard or custom, that you want to
+                            delete records from.
+  -w, --wait=<value>        [default: [object Object]] Number of minutes to wait for the command to complete before
+                            displaying the results.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
-EXAMPLES
-  Stream log output:
+GLOBAL FLAGS
+  --json  Format output as json.
 
-    $ sf env log --target-compute environment-alias
-```
+DESCRIPTION
+  Bulk delete records from an org using a CSV file. Uses Bulk API 1.0.
 
-## `sf env log tail`
+  The CSV file must have only one column ("Id") and then the list of record IDs you want to delete, one ID per line.
 
-Stream log output for an environment.
+  When you execute this command, it starts a job and one or more batches, displays their IDs, and then immediately
+  returns control of the terminal to you by default. If you prefer to wait, set the --wait flag to the number of
+  minutes; if it times out, the command outputs the IDs. Use the job and batch IDs to check the status of the job with
+  the "sf force data bulk status" command. A single job can contain many batches, depending on the length of the CSV
+  file.
 
-```
-USAGE
-  $ sf env log tail [-e <value> | ]
+EXAMPLES
+  Bulk delete Account records from your default org using the list of IDs in the "files/delete.csv" file:
 
-FLAGS
-  -e, --target-compute=<value>  Compute environment name to retrieve logs.
+    $ sf force data bulk delete --sobject Account --file files/delete.csv
 
-EXAMPLES
-  Stream log output:
+  Bulk delete records from a custom object in an org with alias my-scratch and wait 5 minutes for the command to
+  complete:
 
-    $ sf env log tail --target-compute environment-alias
+    $ sf force data bulk delete --sobject MyObject__c --file files/delete.csv --wait 5 --target-org my-scratch
 ```
 
-## `sf env logdrain add`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/force/data/bulk/delete.ts)_
 
-Add log drain to a specified environment.
+## `sf force data bulk status`
+
+View the status of a bulk data load job or batch. Uses Bulk API 1.0.
 
 ```
 USAGE
-  $ sf env logdrain add [--json] [-e <value> | ] [-l <value> | ]
+  $ sf force data bulk status -o <value> -i <value> [--json] [--api-version <value>] [-b <value>]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
-  -l, --drain-url=<value>       Endpoint that will receive sent logs.
+  -b, --batch-id=<value>    ID of the batch whose status you want to view; you must also specify the job ID.
+  -i, --job-id=<value>      (required) ID of the job whose status you want to view.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Add log drain to a specified environment.
+  View the status of a bulk data load job or batch. Uses Bulk API 1.0.
 
-  Both '--target-compute' and '--url' are required flags. '--url' should be a HTTP or HTTPS URL that can receive the log
-  drain messages.
+  Run this command using the job ID or batch ID returned from the "sf force data bulk delete" or "sf force data bulk
+  upsert" commands.
 
 EXAMPLES
-  Add a log drain:
+  View the status of a bulk load job in your default org:
+
+    $ sf force data bulk status --job-id 750xx000000005sAAA
 
-    $ sf env logdrain add --target-compute environment-name --url https://path/to/logdrain
+  View the status of a bulk load job and a specific batches in an org with alias my-scratch:
+
+    $ sf force data bulk status --job-id 750xx000000005sAAA --batch-id 751xx000000005nAAA --target-org my-scratch
 ```
 
-## `sf env logdrain list`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/force/data/bulk/status.ts)_
+
+## `sf force data bulk upsert`
 
-List log drains connected to a specified environment.
+Bulk upsert records to an org from a CSV file. Uses Bulk API 1.0.
 
 ```
 USAGE
-  $ sf env logdrain list [--json] [-e <value> | ]
+  $ sf force data bulk upsert -o <value> -i <value> -f <value> -s <value> [--json] [--api-version <value>] [-w <value>]
+  [-r]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
+  -f, --file=<value>         (required) CSV file that contains the records to upsert.
+  -i, --external-id=<value>  (required) Name of the external ID field, or the Id field.
+  -o, --target-org=<value>   (required) Username or alias of the target org.
+  -r, --serial               Run batches in serial mode.
+  -s, --sobject=<value>      (required) API name of the Salesforce object, either standard or custom, that you want to
+                             upsert records to.
+  -w, --wait=<value>         [default: [object Object]] Number of minutes to wait for the command to complete before
+                             displaying the results.
+  --api-version=<value>      Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
+DESCRIPTION
+  Bulk upsert records to an org from a CSV file. Uses Bulk API 1.0.
+
+  An upsert refers to inserting a record into a Salesforce object if the record doesn't already exist, or updating it if
+  it does exist.
+
+  When you execute this command, it starts a job and one or more batches, displays their IDs, and then immediately
+  returns control of the terminal to you by default. If you prefer to wait, set the --wait flag to the number of
+  minutes; if it times out, the command outputs the IDs. Use the job and batch IDs to check the status of the job with
+  the "sf force data bulk status" command. A single job can contain many batches, depending on the length of the CSV
+  file.
+
+  See "Prepare CSV Files" in the Bulk API Developer Guide for details on formatting your CSV file.
+  (https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/datafiles_csv_preparing.htm)
+
+  By default, the job runs the batches in parallel, which we recommend. You can run jobs serially by specifying the
+  --serial flag. But don't process data in serial mode unless you know this would otherwise result in lock timeouts and
+  you can't reorganize your batches to avoid the locks.
+
 EXAMPLES
-  List log drains:
+  Bulk upsert records to the Contact object in your default org:
 
-    $ sf env logdrain list --target-compute environment-alias
+    $ sf --sobject Contact --file files/contacts.csv --external-id Id
 
-  List log drains as json:
+  Bulk upsert records to a custom object in an org with alias my-scratch and wait 5 minutes for the command to
+  complete:
 
-    $ sf env logdrain list --target-compute environment-alias --json
+    $ sf force data bulk upsert --sobject MyObject__c --file files/file.csv --external-id MyField__c --wait 5 \
+      --target-org my-scratch
 ```
 
-## `sf env logdrain remove`
+_See code: [@salesforce/plugin-data](https://github.com/salesforcecli/plugin-data/blob/2.5.14/src/commands/force/data/bulk/upsert.ts)_
+
+## `sf force mdapi deploy`
 
-Remove log drain from a specified environment.
+Deploy metadata to an org using Metadata API.
 
 ```
 USAGE
-  $ sf env logdrain remove [--json] [-e <value> | ] [-l <value> | ]
+  $ sf force mdapi deploy -u <value> [--json] [--api-version <value>] [-d <value>] [-w <value>] [-o] [-g] [-q <value> |
+    -l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg | -r <value> | -c] [--verbose] [-f <value>] [-s]
+    [--soapdeploy] [--purgeondelete] [--concise] [--resultsdir <value>] [--coverageformatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
-  -l, --drain-url=<value>       Log drain url to remove.
+  -c, --checkonly
+      Validates the deployed metadata and runs all Apex tests, but prevents the deployment from being saved to the org.
 
-GLOBAL FLAGS
-  --json  Format output as json.
+  -d, --deploydir=<value>
+      Root of directory tree that contains the files you want to deploy.
 
-DESCRIPTION
-  Remove log drain from a specified environment.
+  -f, --zipfile=<value>
+      Path to .zip file of metadata to deploy.
 
-  Both '--target-compute' and '--drain-url' are required flags.
+  -g, --ignorewarnings
+      Ignore any warnings and don't roll back the deployment.
 
-EXAMPLES
-  Remove a logdrain:
+  -l, --testlevel=<option>
+      Level of deployment tests to run.
+      <options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
 
-    $ sf env logdrain remove --target-compute environment-alias --url https://path/to/logdrain
-```
+  -o, --ignoreerrors
+      Ignore any errors and don't roll back the deployment.
 
-## `sf env open`
+  -q, --validateddeployrequestid=<value>
+      Request ID of the validated deployment to run a Quick Deploy.
 
-Open an environment in a web browser.
+  -r, --runtests=<value>...
+      Apex test classes to run if --testlevel is RunSpecifiedTests.
 
-```
-USAGE
-  $ sf env open [--json] [-p <value>] [-r] [-e <value>] [--browser <value>]
+  -s, --singlepackage
+      Indicates that the zip file points to a directory structure for a single package.
 
-FLAGS
-  -e, --target-env=<value>  Login user or alias of the environment to open.
-  -p, --path=<value>        Path to append to the end of the login URL.
-  -r, --url-only            Display the URL, but don’t launch it in a browser.
-  --browser=<value>         Browser in which to open the environment.
+  -u, --target-org=<value>
+      (required) Username or alias of the target org.
 
-GLOBAL FLAGS
-  --json  Format output as json.
+  -w, --wait=<value>
+      [default: [object Object]] Number of minutes to wait for the command to finish; specify -1 to wait indefinitely.
 
-DESCRIPTION
-  Open an environment in a web browser.
+  --api-version=<value>
+      Override the api version used for api requests made by this command
 
-  You can open the following types of environments in a web browser: scratch orgs, sandboxes, Dev Hubs, and production
-  orgs. Run "sf env list" to view your environments and their aliases and login usernames.
+  --concise
+      Omit success messages for smaller JSON output.
 
-  Each of your environments is associated with an instance URL, such as https://login.salesforce.com. To open a specific
-  web page, specify the portion of the URL after "<URL>/" with the --path flag, such as /apex/YourPage to open a
-  Visualforce page.
+  --coverageformatters=clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary...
+      Format of the code coverage results.
 
-EXAMPLES
-  Open the Visualforce page /apex/StartHere in a scratch org with alias test-org:
+  --junit
+      Output JUnit test results.
 
-    $ sf env open --target-env test-org --path /apex/StartHere
+  --purgeondelete
+      Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion
+      rather than being stored in the Recycle Bin.
 
-  View the URL but don't launch it in a browser:
+  --resultsdir=<value>
+      Output directory for code coverage and JUnit results; defaults to the deploy ID.
 
-    $ sf env open --target-env test-org --path /apex/StartHere --url-only
+  --soapdeploy
+      Deploy metadata with SOAP API instead of REST API.
 
-  Open the environment in the Google Chrome browser:
+  --verbose
+      Display verbose output of the deploy results.
 
-    $ sf env open --target-env test-org --path /apex/StartHere --browser chrome
+GLOBAL FLAGS
+  --json  Format output as json.
 
-FLAG DESCRIPTIONS
-  -e, --target-env=<value>  Login user or alias of the environment to open.
+EXAMPLES
+  Return a job ID you can use to check the deploy status:
 
-    Specify the login user or alias that’s associated with the environment. For scratch orgs, the login user is
-    generated by the command that created the scratch org. You can also set an alias for the scratch org when you create
-    it.
+    $ sf force mdapi deploy --deploydir some/path
 
-    For Dev Hubs, sandboxes, and production orgs, specify the alias you set when you logged into the org with "sf
-    login".
+  Deploy and poll for 1000 minutes:
 
-  --browser=<value>  Browser in which to open the environment.
+    $ sf force mdapi deploy --deploydir some/path --wait 1000
 
-    You can specify that the environment open in one of the following browsers: Firefox, Safari, Google Chrome, or
-    Windows Edge. If you don’t specify --browser, the environment opens in your default browser. The exact names of the
-    browser applications differ depending on the operating system you're on; check your documentation for details.
-```
+  Deploy a ZIP file:
 
-## `sf env resume sandbox`
+    $ sf force mdapi deploy --zipfile stuff.zip
 
-Check the status of a sandbox creation, and log in to it if it's ready.
+  Validate a deployment so the ID can be used for a quick deploy:
 
-```
-USAGE
-  $ sf env resume sandbox [--json] [-w <value>] [-n <value> | -i <value>] [-l] [-o <value>]
+    $ sf force mdapi deploy --deploydir some/path --wait 1000 --checkonly --testlevel RunAllTestsInOrg
 
-FLAGS
-  -i, --job-id=<value>      Job ID of the incomplete sandbox creation that you want to check the status of.
-  -l, --use-most-recent     Use the most recent sandbox create request.
-  -n, --name=<value>        Name of the sandbox org.
-  -o, --target-org=<value>  Username or alias of the production org that contains the sandbox license.
-  -w, --wait=<minutes>      Number of minutes to wait for the sandbox org to be ready.
+  Quick deploy using a previously validated deployment:
 
-GLOBAL FLAGS
-  --json  Format output as json.
+    $ sf force mdapi deploy --validateddeployrequestid MyValidatedId
 
-DESCRIPTION
-  Check the status of a sandbox creation, and log in to it if it's ready.
+FLAG DESCRIPTIONS
+  -c, --checkonly
 
-  Sandbox creation can take a long time. If the original "sf env create sandbox" command either times out, or you
-  specified the --async flag, the command displays a job ID. Use this job ID to check whether the sandbox creation is
-  complete, and if it is, the command then logs into it.
+    Validates the deployed metadata and runs all Apex tests, but prevents the deployment from being saved to the org.
 
-  You can also use the sandbox name to check the status or the --use-most-recent flag to use the job ID of the most
-  recent sandbox creation.
+    IMPORTANT: Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained
+    certain terms to avoid any effect on customer implementations.
 
-EXAMPLES
-  Check the status of a sandbox creation using its name and specify a production org with alias "prodOrg":
+    If you change a field type from Master-Detail to Lookup or vice versa, that change isn’t supported when using the
+    --checkonly parameter to test a deployment (validation). This kind of change isn’t supported for test deployments to
+    avoid the risk of data loss or corruption. If a change that isn’t supported for test deployments is included in a
+    deployment package, the test deployment fails and issues an error.
 
-    $ sf env resume sandbox --name mysandbox --target-org prodOrg
+    If your deployment package changes a field type from Master-Detail to Lookup or vice versa, you can still validate
+    the changes prior to deploying to Production by performing a full deployment to another test Sandbox. A full
+    deployment includes a validation of the changes as part of the deployment process.
 
-  Check the status using the job ID:
+    Note: A Metadata API deployment that includes Master-Detail relationships deletes all detail records in the Recycle
+    Bin in the following cases.
 
-    $ sf env resume sandbox --job-id 0GRxxxxxxxx
+    1. For a deployment with a new Master-Detail field, soft delete (send to the Recycle Bin) all detail records before
+    proceeding to deploy the Master-Detail field, or the deployment fails. During the deployment, detail records are
+    permanently deleted from the Recycle Bin and cannot be recovered.
+    2. For a deployment that converts a Lookup field relationship to a Master-Detail relationship, detail records must
+    reference a master record or be soft-deleted (sent to the Recycle Bin) for the deployment to succeed. However, a
+    successful deployment permanently deletes any detail records in the Recycle Bin.
 
-  Check the status of the most recent sandbox create request:
+  -d, --deploydir=<value>  Root of directory tree that contains the files you want to deploy.
 
-    $ sf env resume sandbox --use-most-recent
+    The root must contain a valid package.xml file describing the entities in the directory structure. Required to
+    initiate a deployment if you don’t use --zipfile. If you specify both --zipfile and --deploydir, a zip file of the
+    contents of the --deploydir directory is written to the location specified by --zipfile.
 
-FLAG DESCRIPTIONS
-  -i, --job-id=<value>  Job ID of the incomplete sandbox creation that you want to check the status of.
+  -f, --zipfile=<value>  Path to .zip file of metadata to deploy.
 
-    The job ID is valid for 24 hours after you start the sandbox creation.
+    You must indicate this option or --deploydir. If you specify both --zipfile and --deploydir, a .zip file of the
+    contents of the deploy directory is created at the path specified for the .zip file.
 
-  -o, --target-org=<value>  Username or alias of the production org that contains the sandbox license.
+  -g, --ignorewarnings  Ignore any warnings and don't roll back the deployment.
 
-    When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to
-    the new sandbox org.
+    If a warning occurs and ignoreWarnings is set to true, the success field in DeployMessage is true. When
+    ignoreWarnings is set to false, success is set to false, and the warning is treated like an error.
+    This field is available in API version 18.0 and later. Prior to version 18.0, there was no distinction between
+    warnings and errors. All problems were treated as errors and prevented a successful deployment.
 
-  -w, --wait=<minutes>  Number of minutes to wait for the sandbox org to be ready.
+  -l, --testlevel=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg  Level of deployment tests to run.
 
-    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
-    returns the job ID. To resume checking the sandbox creation, rerun this command.
-```
+    Valid values are:
 
-## `sf env resume scratch`
+    * NoTestRun—No tests are run. This test level applies only to deployments to development environments, such as
+    sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.
+    * RunSpecifiedTests—Runs only the tests that you specify in the --runtests option. Code coverage requirements differ
+    from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75%
+    code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
+    trigger individually and is different than the overall coverage percentage.
+    * RunLocalTests—All tests in your org are run, except the ones that originate from installed managed and unlocked
+    packages. This test level is the default for production deployments that include Apex classes or triggers.
+    * RunAllTestsInOrg—All tests in your org are run, including tests of managed packages.
 
-Resume the creation of an incomplete scratch org.
+    If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more
+    information, see “Running Tests in a Deployment” in the Metadata API Developer Guide.
 
-```
-USAGE
-  $ sf env resume scratch [--json] [-i <value>] [-r]
+  -o, --ignoreerrors  Ignore any errors and don't roll back the deployment.
 
-FLAGS
-  -i, --job-id=<value>   Job ID of the incomplete scratch org create that you want to resume.
-  -r, --use-most-recent  Use the job ID of the most recent incomplete scratch org.
+    The default is false. Keep this parameter set to false when deploying to a production org. If set to true,
+    components without errors are deployed, and components with errors are skipped.
 
-GLOBAL FLAGS
-  --json  Format output as json.
+  -q, --validateddeployrequestid=<value>  Request ID of the validated deployment to run a Quick Deploy.
 
-DESCRIPTION
-  Resume the creation of an incomplete scratch org.
+    Deploying a validation helps you shorten your deployment time because tests aren’t rerun. If you have a recent
+    successful validation, you can deploy the validated components without running tests. A validation doesn’t save any
+    components in the org. You use a validation only to check the success or failure messages that you would receive
+    with an actual deployment. To validate your components, add the -c | --checkonly flag when you run 'force mdapi
+    deploy'. This flag sets the checkOnly='true' parameter for your deployment. Before deploying a recent validation,
+    ensure that the following requirements are met:
 
-  When the original "sf env create scratch" command either times out or is run with the --async flag, it displays a job
-  ID.
+    1. The components have been validated successfully for the target environment within the last 10 days.
+    2. As part of the validation, Apex tests in the target org have passed.
+    3. Code coverage requirements are met.
+    - If all tests in the org or all local tests are run, overall code coverage is at least 75%, and Apex triggers have
+    some coverage.
+    - If specific tests are run with the RunSpecifiedTests test level, each class and trigger that was deployed is
+    covered by at least 75% individually.
 
-  Run this command by either passing it a job ID or using the --use-most-recent flag to specify the most recent
-  incomplete scratch org.
+  -s, --singlepackage  Indicates that the zip file points to a directory structure for a single package.
 
-EXAMPLES
-  Resume a scratch org create with a job ID:
+    By default, the CLI assumes the directory is structured for a set of packages.
 
-    $ sf env resume scratch --job-id 2SR3u0000008fBDGAY
+  -w, --wait=<value>  Number of minutes to wait for the command to finish; specify -1 to wait indefinitely.
 
-  Resume your most recent incomplete scratch org:
+    The default is 0 (returns immediately).
 
-    $ sf env resume scratch --use-most-recent
+  --soapdeploy  Deploy metadata with SOAP API instead of REST API.
 
-FLAG DESCRIPTIONS
-  -i, --job-id=<value>  Job ID of the incomplete scratch org create that you want to resume.
+    Because SOAP API has a lower .ZIP file size limit (400 MB uncompressed, 39 MB compressed), Salesforce recommends
+    REST API deployment. This flag provides backwards compatibility with API version 50.0 and earlier when deploy used
+    SOAP API by default.
 
-    The job ID is the same as the record ID of the incomplete scratch org in the ScratchOrgInfo object of the Dev Hub.
+  --verbose  Display verbose output of the deploy results.
 
-    The job ID is valid for 24 hours after you start the scratch org creation.
+    Indicates that you want verbose output from the deploy operation.
 ```
 
-## `sf env var get KEY`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/mdapi/deploy.ts)_
 
-Display a single config variable for an environment.
+## `sf force mdapi deploy cancel`
+
+Cancel a metadata deployment.
 
 ```
 USAGE
-  $ sf env var get [KEY] [--json] [-e <value> | ]
+  $ sf force mdapi deploy cancel -o <value> [--json] [--api-version <value>] [-w <value>] [-i <value>]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
+  -i, --jobid=<value>       Job ID of the deployment you want to cancel; defaults to your most recent CLI deployment.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -w, --wait=<value>        [default: [object Object]] Number of minutes for the command to complete and display results
+                            to the terminal window.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Display a single config variable for an environment.
+  Cancel a metadata deployment.
+
+  Use this command to cancel a specified asynchronous metadata deployment. You can also specify a wait time (in minutes)
+  to check for updates to the canceled deploy status.
 
-  You must provide the '--target-compute' flag and the key to retrieve.
+  Cancels an asynchronous metadata deployment.
 
 EXAMPLES
-  Get a config variable:
+  Cancel a deployment and wait two minutes:
+
+    $ sf force mdapi deploy cancel --wait 2
+
+  If you have multiple deployments in progress and want to cancel a specific one, specify the job ID:
+
+    $ sf force mdapi deploy cancel --jobid <jobid>
+
+FLAG DESCRIPTIONS
+  -w, --wait=<value>  Number of minutes for the command to complete and display results to the terminal window.
 
-    $ sf env var get [KEY] --target-compute environment-alias
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
 ```
 
-## `sf env var list`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/mdapi/deploy/cancel.ts)_
 
-List your environment's config vars in a table.
+## `sf force mdapi deploy report`
+
+Check the status of a metadata deployment.
 
 ```
 USAGE
-  $ sf env var list [--json] [-e <value> | ]
+  $ sf force mdapi deploy report -o <value> [--json] [--api-version <value>] [-w <value>] [-i <value>] [--verbose] [--concise]
+    [--resultsdir <value>] [--coverageformatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
+  -i, --jobid=<value>
+      Job ID of the deployment to check; required if you’ve never deployed using Salesforce CLI; defaults to your most
+      recent CLI deployment.
+
+  -o, --target-org=<value>
+      (required) Username or alias of the target org.
+
+  -w, --wait=<value>
+      [default: [object Object]] Number of minutes to wait for the command to finish; use -1 to poll indefinitely.
+
+  --api-version=<value>
+      Override the api version used for api requests made by this command
+
+  --concise
+      Omit success messages for smaller JSON output.
+
+  --coverageformatters=clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary...
+      Format of the code coverage results.
+
+  --junit
+      Output JUnit test results.
+
+  --resultsdir=<value>
+      Output directory for code coverage and JUnit results; defaults to the deploy ID.
+
+  --verbose
+      Verbose output of deploy results.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List your environment's config vars in a table.
+  Check the status of a metadata deployment.
 
-  Use the '--json' flag to return config vars in JSON format.
+  Specify the job ID for the deploy you want to check. The job ID is returned by the "force mdapi deploy" command when
+  run without the --wait parameter. You can also specify a wait time (minutes) to check for updates to the deploy
+  status.
 
 EXAMPLES
-  List config vars:
+  Check the status of the most recent deployment
 
-    $ sf env var list --target-compute environment-alias
+    $ sf force mdapi deploy report
 
-  List in JSON format:
+  Check the status of a deploy with job ID 1234 and wait for 10 minutes for the result:
 
-    $ sf env var list --target-compute environment-alias --json
-```
+    $ sf force mdapi deploy report --jobid 1234 --wait 10
 
-## `sf env var set`
+FLAG DESCRIPTIONS
+  -i, --jobid=<value>
 
-Set a single config value for an environment.
+    Job ID of the deployment to check; required if you’ve never deployed using Salesforce CLI; defaults to your most
+    recent CLI deployment.
 
+    The job ID (id field value for AsyncResult) of the deployment you want to check. The job ID is required if you
+    haven’t previously deployed using Salesforce CLI. If you deploy using Salesforce CLI and don’t specify a job ID, we
+    use the ID of the most recent metadata deployment.
 ```
-USAGE
-  $ sf env var set [--json] [-e <value> | ]
-
-FLAGS
-  -e, --target-compute=<value>  Environment name.
 
-GLOBAL FLAGS
-  --json  Format output as json.
-
-EXAMPLES
-  Set a config value:
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/mdapi/deploy/report.ts)_
 
-    $ sf env var set [KEY]=[VALUE] --target-compute environment-alias
-```
-
-## `sf env var unset`
+## `sf force mdapi retrieve`
 
-Unset a single config value for an environment.
+Retrieve metadata from an org using Metadata API.
 
 ```
 USAGE
-  $ sf env var unset [--json] [-e <value> | ]
+  $ sf force mdapi retrieve -o <value> -r <value> [--json] [-k <value> | -d <value> | -p <value>] [-s] [-n <value>] [-z]
+    [-w <value>] [-a <value>] [--verbose]
 
 FLAGS
-  -e, --target-compute=<value>  Environment name.
+  -a, --apiversion=<value>         Target API version for the retrieve.
+  -d, --sourcedir=<value>          Source directory to use instead of the default package directory specified in
+                                   sfdx-project.json.
+  -k, --unpackaged=<value>         Complete path for the manifest file that specifies the components to retrieve.
+  -n, --zipfilename=<value>        File name to use for the retrieved zip file.
+  -o, --target-org=<value>         (required) Username or alias of the target org.
+  -p, --packagenames=<value>...    Comma-separated list of packages to retrieve.
+  -r, --retrievetargetdir=<value>  (required) Root of the directory structure where the retrieved .zip or metadata files
+                                   are retrieved.
+  -s, --singlepackage              Specify that the zip file points to a directory structure for a single package.
+  -w, --wait=<value>               [default: [object Object]] Number of minutes to wait for the command to complete.
+  -z, --unzip                      Extract all files from the retrieved zip file.
+  --verbose                        Display verbose output of retrieve result.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Unset a single config value for an environment.
+  Retrieve metadata from an org using Metadata API.
 
-  Run 'sf env var list' to see a list of config values that can be unset.
+  This command uses Metadata API to retrieve a .zip of XML files that represent metadata from the targeted org. You can
+  retrieve and deploy up to 10,000 files or 400 MB (39 MB compressed) at one time.
 
 EXAMPLES
-  Unset a value:
+  Retrieve metadata in the default project directory into the target directory:
 
-    $ sf env var unset --target-compute environment-alias
-```
+    $ sf force mdapi retrieve --retrievetargetdir path/to/retrieve/dir
 
-## `sf generate function`
+  Retrieve metadata defined in the specified manifest into the target directory:
 
-Create a Salesforce Function with basic scaffolding specific to a given language.
+    $ sf force mdapi retrieve --retrievetargetdir path/to/retrieve/dir --unpackaged package.xml
 
-```
-USAGE
-  $ sf generate function -l javascript|typescript|java [-n <value> | ]
+  Retrieve metadata defined by the specified directory, name the retrieved zipfile and extract all contents
 
-FLAGS
-  -l, --language=(javascript|typescript|java)  (required) Language. Can be one of: javascript, typescript, java.
-  -n, --function-name=<value>                  Function name. Must start with a capital letter.
+    $ sf force mdapi retrieve --sourcedir path/to/apexClasses --retrievetargetdir path/to/retrieve/dir --unzip \
+      --zipfilename apexClasses.zip
 
-DESCRIPTION
-  Create a Salesforce Function with basic scaffolding specific to a given language.
+  Enqueue a retrieve request but do not wait for the metadata to be retrieved:
 
-  Both '--language' and '--name' are required flags. Function names must start with a capital letter.
+    $ sf force mdapi retrieve --retrievetargetdir path/to/retrieve/dir --wait 0
 
-EXAMPLES
-  Create a JavaScript function:
+FLAG DESCRIPTIONS
+  -a, --apiversion=<value>  Target API version for the retrieve.
+
+    Use to override the default, which is the latest version supported by your CLI plug-in, with the version in your
+    package.xml file.
 
-    $ sf generate function --function-name myfunction --language javascript
+  -s, --singlepackage  Specify that the zip file points to a directory structure for a single package.
+
+    By default, the CLI assumes the directory is structured for a set of packages.
 ```
 
-## `sf generate metadata field`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/mdapi/retrieve.ts)_
 
-Generate metadata source files for a new custom field on a specified object.
+## `sf force mdapi retrieve report`
+
+Check the status of a metadata retrieval.
 
 ```
 USAGE
-  $ sf generate metadata field -l <value> [-o <value>]
+  $ sf force mdapi retrieve report -o <value> [--json] [--api-version <value>] [-r <value>] [-i <value>] [-n <value>] [-z] [-w
+    <value>] [--verbose]
 
 FLAGS
-  -l, --label=<value>   (required) The field's label.
-  -o, --object=<value>  The directory that contains the object's source files.
+  -i, --jobid=<value>              Job ID of the retrieve you want to check; defaults to your most recent CLI retrieval.
+  -n, --zipfilename=<value>        File name to use for the retrieved zip file.
+  -o, --target-org=<value>         (required) Username or alias of the target org.
+  -r, --retrievetargetdir=<value>  Root of the directory structure where the retrieved .zip or metadata files are
+                                   retrieved.
+  -w, --wait=<value>               [default: [object Object]] Number of minutes to wait for the command to complete.
+  -z, --unzip                      Extract all files from the retrieved zip file.
+  --api-version=<value>            Override the api version used for api requests made by this command
+  --verbose                        Display verbose output of retrieve result.
 
-DESCRIPTION
-  Generate metadata source files for a new custom field on a specified object.
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  This command is interactive and must be run in a Salesforce DX project directory. You're required to specify the
-  field's label with the "--label" flag. The command uses this label to provide intelligent suggestions for other field
-  properties, such as its API name.
+DESCRIPTION
+  Check the status of a metadata retrieval.
 
-  You can generate a custom field on either a standard object, such as Account, or a custom object. In both cases, the
-  source files for the object must already exist in your local project before you run this command. If you create a
-  relationship field, the source files for the parent object must also exist in your local directory.  Use the command
-  "sf metadata retrieve -m CustomObject:<object>" to retrieve source files for both standard and custom objects from
-  your org.  To create a custom object, run the "sf generate metadata sobject" command or use the Object Manager UI in
-  your Salesforce org.
+  Specify the job ID and a target directory for the retrieve you want to check. You can also specify a wait time
+  (minutes) to check for updates to the retrieve status. If the retrieve was successful, the resulting zip file will be
+  saved to the location passed in with the retrieve target parameter.
 
 EXAMPLES
-  Create a field with the specified label; the command prompts you for the object:
+  Poll until the metadata is retrieved (or timeout is reached) using data from the last force:mdapi:retrieve command:
 
-    $ sf generate metadata field --label "My Field"
+    $ sf force mdapi retrieve report
 
-  Specify the local path to the object's folder:
+  Report the current status of the last retrieve command. If the retrieve is complete the zip file of metadata is
+  written to the target directoy:
 
-    $ sf generate metadata field --label "My Field" --object force-app/main/default/objects/MyObject__c
+    $ sf force mdapi retrieve report --retrievetargetdir path/to/retrieve/dir --wait 0
 
-FLAG DESCRIPTIONS
-  -o, --object=<value>  The directory that contains the object's source files.
+  Poll until the metadata is retrieved (or timeout is reached) using the provided RetrieveID, naming the zip file and
+  extracting all contents:
 
-    The object source files in your local project are grouped in a directoy with the same name as the object. Custom
-    object names always end in "__c". An example of the object directory for the Account standard object is
-    "force-app/main/default/objects/Account" An example custom object directory is
-    "force-app/main/default/objects/MyObject__c"
+    $ sf force mdapi retrieve report -i retrieveId --retrievetargetdir path/to/retrieve/dir --unzip --zipfilename \
+      apexClasses.zip
 
-    If you don't specify this flag, the command prompts you to choose from your local objects.
+FLAG DESCRIPTIONS
+  -i, --jobid=<value>  Job ID of the retrieve you want to check; defaults to your most recent CLI retrieval.
+
+    You must specify a --retrievetargetdir. Use with --wait to resume waiting.
 ```
 
-## `sf generate metadata platformevent`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/mdapi/retrieve/report.ts)_
 
-Generate metadata source files for a new platform event.
+## `sf force org clone`
+
+Clone a sandbox org.
 
 ```
 USAGE
-  $ sf generate metadata platformevent -l <value>
+  $ sf force org clone -o <value> -t sandbox [--json] [--api-version <value>] [-f <value>] [-s] [-a <value>] [-w
+    <value>]
 
 FLAGS
-  -l, --label=<value>  (required) The platform event's label.
+  -a, --setalias=<value>        Alias for the cloned org.
+  -f, --definitionfile=<value>  Path to the sandbox definition file.
+  -o, --target-org=<value>      (required) Username or alias of the target org.
+  -s, --setdefaultusername      Set the cloned org as your default.
+  -t, --type=<option>           (required) Type of org to create.
+                                <options: sandbox>
+  -w, --wait=<value>            [default: [object Object]] Number of minutes to wait while polling for status.
+  --api-version=<value>         Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Generate metadata source files for a new platform event.
+  Clone a sandbox org.
 
-  This command is interactive and must be run in a Salesforce DX project directory. You're required to specify the
-  event's label with the "--label" flag. The command uses this label to provide intelligent suggestions for other event
-  properties, such as its API name.
+  There are two ways to clone a sandbox: either specify a sandbox definition file or provide key=value pairs at the
+  command line. Key-value pairs at the command-line override their equivalent sandbox definition file values. In either
+  case, you must specify both the "SandboxName" and "SourceSandboxName" options to set the names of the new sandbox and
+  the one being cloned, respectively.
+
+  Set the --targetusername (-u) parameter to a production org with sandbox licenses. The --type (-t) parameter is
+  required and must be set to "sandbox".
 
 EXAMPLES
-  Create a platform event with the specified label:
+  $ sf force org clone -t sandbox -f config/dev-sandbox-def.json -u prodOrg -a MyDevSandbox
 
-    $ sf generate metadata platformevent --label "My Platform Event"
+  $ sf force org clone -t sandbox SandboxName=NewClonedSandbox SourceSandboxName=ExistingSandbox -u prodOrg -a MyDevSandbox
+
+FLAG DESCRIPTIONS
+  -w, --wait=<value>  Number of minutes to wait while polling for status.
+
+    Sets the streaming client socket timeout, in minutes. If the streaming client socket has no contact from the server
+    for a number of minutes, the client exits. Specify a longer wait time if timeouts occur frequently.
 ```
 
-## `sf generate metadata sobject`
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/force/org/clone.ts)_
 
-Generate metadata source files for a new custom object.
+## `sf force org create`
+
+Create a scratch org or sandbox.
 
 ```
 USAGE
-  $ sf generate metadata sobject -l <value> [-f]
+  $ sf force org create [--json] [-o <value>] [-v <value>] [--api-version <value>] [-t scratch|sandbox] [-f <value>]
+    [-n] [-c] [-i <value>] [-s] [-a <value>] [-w <value>] [-d <value>]
 
 FLAGS
-  -f, --use-default-features  Enable all optional features without prompting.
-  -l, --label=<value>         (required) The custom object's label.
-
-DESCRIPTION
-  Generate metadata source files for a new custom object.
+  -a, --setalias=<value>        Alias for the created org.
+  -c, --noancestors             Do not include second-generation package ancestors in the scratch org.
+  -d, --durationdays=<value>    [default: 7] Duration of the scratch org (in days) (default:7, min:1, max:30).
+  -f, --definitionfile=<value>  Path to an org definition file.
+  -i, --clientid=<value>        Connected app consumer key; not supported for sandbox org creation.
+  -n, --nonamespace             Create the scratch org with no namespace.
+  -o, --target-org=<value>      Username or alias of the production org that contains the sandbox license.
+  -s, --setdefaultusername      Set the created org as the default username.
+  -t, --type=<option>           [default: scratch] Type of org to create.
+                                <options: scratch|sandbox>
+  -v, --target-dev-hub=<value>  Username or alias of the Dev Hub org.
+  -w, --wait=<value>            [default: [object Object]] Streaming client socket timeout (in minutes).
+  --api-version=<value>         Override the api version used for api requests made by this command
 
-  This command is interactive and must be run in a Salesforce DX project directory. You're required to specify the
-  object's label with the "--label" flag. The command uses this label to provide intelligent suggestions for other
-  object properties, such as its API name and plural label.
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  All Salesforce objects are required to have a Name field, so this command also prompts you for the label and type of
-  the Name field. Run the "sf metadata generate field" command to create additional fields for the object.
+DESCRIPTION
+  Create a scratch org or sandbox.
 
-  To reduce the number of prompts, use the "--use-default-features" flag to automatically enable some features, such as
-  reporting and search on the object.
+  Creates a scratch org or a sandbox org using the values specified in a configuration file or key=value pairs that you
+  specify on the command line. Values specified on the command line override values in the configuration file. Specify a
+  configuration file or provide key=value pairs while creating a scratch org or a sandbox. When creating scratch orgs,
+  —targetdevhubusername (-v) must be a Dev Hub org. When creating sandboxes, the --targetusername (-u) must be a
+  production org with sandbox licenses. The —type (-t) is required if creating a sandbox.
 
 EXAMPLES
-  Create a custom object with the specified label and be prompted for additional information:
-
-    $ sf generate metadata sobject --label "My Object"
-
-  Create a custom object and enable optional features without prompting:
-
-    $ sf generate metadata sobject --label "My Object" --use-default-features
+  $ sf force org create -f config/enterprise-scratch-def.json -a MyScratchOrg
 
-FLAG DESCRIPTIONS
-  -f, --use-default-features  Enable all optional features without prompting.
+  $ sf force org create edition=Developer -a MyScratchOrg -s -v devHub
 
-    Enables these features:
+  $ sf force org create -f config/enterprise-scratch-def.json -a ScratchOrgWithOverrides username=testuser1@mycompany.org
 
-    * Search: Allows users to find the custom object's records when they search, including SOSL.
-    * Feeds: Enables feed tracking.
-    * Reports: Allows reporting of the data in the custom object records.
-    * History: Enables object history tracking.
-    * Activities: Allows users to associate tasks and scheduled calendar events related to the custom object records.
-    * Bulk API: With Sharing and Streaming API, classifies the custom object as an Enterprise Application object.
-    * Sharing: With Bulk API and Streaming API, classifies the custom object as an Enterprise Application object.
-    * Streaming API: With Bulk API and Sharing, classifies the custom object as an Enterprise Application object.
+  $ sf force org create -t sandbox -f config/dev-sandbox-def.json -a MyDevSandbox -u prodOrg
 ```
 
-## `sf generate metadata tab`
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/force/org/create.ts)_
 
-Generate the metadata source files for a new custom tab on a custom object.
+## `sf force org delete`
+
+Delete a scratch or sandbox org.
 
 ```
 USAGE
-  $ sf generate metadata tab -o <value> -d <value> -i <value> [--json]
+  $ sf force org delete -o <value> [--json] [--api-version <value>] [-p]
 
 FLAGS
-  -d, --directory=<value>  (required) Path to a "tabs" directory that will contain the source files for your new tab.
-  -i, --icon=<value>       (required) [default: 1] Number from 1 to 100 that specifies the color scheme and icon for the
-                           custom tab.
-  -o, --object=<value>     (required) API name of the custom object you're generating a tab for.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -p, --no-prompt           No prompt to confirm deletion.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Generate the metadata source files for a new custom tab on a custom object.
+  Delete a scratch or sandbox org.
 
-  Custom tabs let you display custom object data or other web content in Salesforce. Custom tabs appear in Salesforce as
-  an item in the app’s navigation bar and in the App Launcher.
+  Salesforce CLI marks the org for deletion in either the Dev Hub org (for scratch orgs) or production org (for
+  sandboxes) and then deletes all local references to the org from your computer.
 
-  This command must be run in a Salesforce DX project directory. You must pass all required information to it with the
-  required flags. The source files for the custom object for which you're generating a tab don't need to exist in your
-  local project.
+  To mark the org for deletion without being prompted to confirm, specify --noprompt.
 
 EXAMPLES
-  Create a tab on the MyObject__c custom object:
-
-    $ sf generate metadata tab --object MyObject__c --icon 54 --directory force-app/main/default/tabs
-
-FLAG DESCRIPTIONS
-  -i, --icon=<value>  Number from 1 to 100 that specifies the color scheme and icon for the custom tab.
-
-    See https://lightningdesignsystem.com/icons/\#custom for the available icons.
+  $ sf force org delete -u me@my.org
 
-  -o, --object=<value>  API name of the custom object you're generating a tab for.
-
-    The API name for a custom object always ends in "__c", such as "MyObject__c".
+  $ sf force org delete -u MyOrgAlias -p
 ```
 
-## `sf generate project`
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/force/org/delete.ts)_
 
-Generate a Salesforce DX project.
+## `sf force org status`
+
+Check the status of a sandbox, and if complete, authenticate to it.
 
 ```
 USAGE
-  $ sf generate project -n <value> [--json] [-p <value>] [-x] [-s <value>] [-d <value>] [-t standard|empty|analytics]
+  $ sf force org status -o <value> -n <value> [--json] [--api-version <value>] [-s] [-a <value>] [-w <value>]
 
 FLAGS
-  -d, --output-dir=<value>           [default: .] Directory to store the newly created project files.
-  -n, --name=<value>                 (required) Name of the generated project.
-  -p, --default-package-dir=<value>  [default: force-app] Default package directory name.
-  -s, --namespace=<value>            Project associated namespace.
-  -t, --template=<option>            [default: standard] Template to use to create the project.
-                                     <options: standard|empty|analytics>
-  -x, --manifest                     Generate a manifest (package.xml) for change-set based development.
+  -a, --setalias=<value>     Alias for the created or cloned org.
+  -n, --sandboxname=<value>  (required) Name of the sandbox org to check status for.
+  -o, --target-org=<value>   (required) Username or alias of the target org.
+  -s, --setdefaultusername   Set the created or cloned org as your default.
+  -w, --wait=<value>         [default: [object Object]] Number of minutes to wait while polling for status.
+  --api-version=<value>      Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Generate a Salesforce DX project.
+  Check the status of a sandbox, and if complete, authenticate to it.
 
-  A Salesforce DX project has a specific structure and a configuration file (sfdx-project.json) that identifies the
-  directory as a Salesforce DX project. This command generates the basic scaffolding to get you started.
+  Use this command to check the status of your sandbox creation or clone and, if the sandbox is ready, authenticate to
+  it.
 
-  By default, the generated sfdx-project.json file sets the sourceApiVersion property to the default API version
-  currently used by Salesforce CLI. To specify a different version, set the apiVersion configuration variable. For
-  example:
+  Use the --wait (-w) parameter to specify the number of minutes that the command waits for the sandbox creation or
+  clone to complete before returning control of the terminal to you.
 
-  sf config set apiVersion=53.0 --global
+  Set the --target-org (-o) parameter to the username or alias of the production org that contains the sandbox license.
 
 EXAMPLES
-  Generate a project called MyProject:
-  ​
-  $ sf generate project --name MyProject
-  ​
-
-  Generate the minimum number of files and directories:
-  ​
-  $ sf generate project --name MyProject --template empty
-  ​
+  $ sf force org status --sandboxname DevSbx1 --setalias MySandbox -u prodOrg
 
-  Generate the project in /Users/jdoe/sf-projects rather than the current directory:
-  ​
-  $ sf generate project --name MyProject --template empty --output-dir /Users/jdoe/sf-projects
+  $ sf force org status --sandboxname DevSbx1 --wait 45 --setdefaultusername -u prodOrg
+```
 
-FLAG DESCRIPTIONS
-  -d, --output-dir=<value>  Directory to store the newly created project files.
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/force/org/status.ts)_
 
-    The location can be an absolute path or relative to the current working directory.
+## `sf force source deploy`
 
-  -n, --name=<value>  Name of the generated project.
+Deploy source to an org.
 
-    Creates a project directory with this name. Also sets the "name" property in the sfdx-project.json file to this
-    name.
+```
+USAGE
+  $ sf force source deploy -u <value> [--json] [--api-version <value>] [--soapdeploy] [-w <value>] [-o] [-g]
+    [--purgeondelete -x <value>] [-q <value> | -c | -l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg | -r
+    <value> | -t] [--verbose] [-m <value>] [-p <value>] [--predestructivechanges <value> ] [--postdestructivechanges
+    <value> ] [-f ] [--resultsdir <value>] [--coverageformatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit]
 
-  -p, --default-package-dir=<value>  Default package directory name.
+FLAGS
+  -c, --checkonly
+      Validate the deployed metadata and run all Apex tests, but don't save to the org.
 
-    The default package directory name. Metadata items such as classes and Lightning bundles are placed inside this
-    folder.
+  -f, --forceoverwrite
+      Ignore conflict warnings and overwrite changes to the org.
 
-  -s, --namespace=<value>  Project associated namespace.
+  -g, --ignorewarnings
+      Allow a deployment to complete successfully even if there are warnings.
 
-    The namespace associated with this project and any connected scratch orgs.
+  -l, --testlevel=<option>
+      Deployment testing level.
+      <options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
 
-  -t, --template=standard|empty|analytics  Template to use to create the project.
+  -m, --metadata=<value>...
+      Comma-separated list of metadata component names.
 
-    The template determines the sample configuration files and directories that this command generates. For example, the
-    empty template provides these files and directory to get you started.
+  -o, --ignoreerrors
+      Ignore any errors and don't roll back deployment.
 
-    - .forceignore
-    - config/project-scratch-def.json
-    - sfdx-project.json
-    - package.json
-    - force-app (basic source directory structure)
+  -p, --sourcepath=<value>...
+      Comma-separated list of source file paths to deploy.
 
-    The standard template provides a complete force-app directory structure so you know where to put your source. It
-    also provides additional files and scripts, especially useful when using Salesforce Extensions for VS Code. For
-    example:
+  -q, --validateddeployrequestid=<value>
+      Deploy request ID of the validated deployment to run a Quick Deploy.
 
-    - .gitignore: Use Git for version control.
-    - .prettierrc and .prettierignore: Use Prettier to format your Aura components.
-    - .vscode/extensions.json: When launched, Visual Studio Code, prompts you to install the recommended extensions for
-    your project.
-    - .vscode/launch.json: Configures Replay Debugger.
-    - .vscode/settings.json: Additional configuration settings.
+  -r, --runtests=<value>...
+      Apex test classes to run if --testlevel RunSpecifiedTests.
 
-    The analytics template provides similar files and the force-app/main/default/waveTemplates directory.
+  -t, --tracksource
+      If the deploy succeeds, update source tracking information.
 
-  -x, --manifest  Generate a manifest (package.xml) for change-set based development.
+  -u, --target-org=<value>
+      (required) Username or alias of the target org.
 
-    Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static
-    resources.
-```
+  -w, --wait=<value>
+      [default: [object Object]] Wait time for command to finish in minutes.
 
-## `sf help [COMMAND]`
+  -x, --manifest=<value>
+      Complete path for the manifest (package.xml) file that specifies the components to deploy.
 
-Display help for sf.
+  --api-version=<value>
+      Override the api version used for api requests made by this command
 
-```
-USAGE
-  $ sf help [COMMAND] [-n]
+  --coverageformatters=clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary...
+      Format of the code coverage results.
 
-ARGUMENTS
-  COMMAND  Command to show help for.
+  --junit
+      Output JUnit test results.
 
-FLAGS
-  -n, --nested-commands  Include all nested commands in the output.
+  --postdestructivechanges=<value>
+      File path for a manifest (destructiveChangesPost.xml) of components to delete after the deploy.
 
-DESCRIPTION
-  Display help for sf.
-```
+  --predestructivechanges=<value>
+      File path for a manifest (destructiveChangesPre.xml) of components to delete before the deploy.
 
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v5.1.12/src/commands/help.ts)_
+  --purgeondelete
+      Specify that deleted components in the destructive changes manifest file are immediately eligible for deletion
+      rather than being stored in the Recycle Bin.
 
-## `sf info:releasenotes:display [-v <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`
+  --resultsdir=<value>
+      Output directory for code coverage and JUnit results; defaults to the deploy ID.
 
-Display Salesforce CLI release notes on the command line.
+  --soapdeploy
+      Deploy metadata with SOAP API instead of REST API.
 
-```
-USAGE
-  $ sf info releasenotes display [-v <string>] [--json] [--loglevel
-    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  --verbose
+      Specify verbose output about the deploy result.
 
-FLAGS
-  -v, --version=<value>                                                             CLI version or tag for which to
-                                                                                    display release notes.
-  --json                                                                            format output as json
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Display Salesforce CLI release notes on the command line.
+  Deploy source to an org.
 
-ALIASES
-  $ sf whatsnew
+  Use this command to deploy source (metadata that’s in source format) to an org. To take advantage of change tracking
+  with scratch orgs, use "force source push". To deploy metadata that’s in metadata format, use "force mdapi deploy".
 
-EXAMPLES
-  Display release notes for the currently installed CLI version:
+  The source you deploy overwrites the corresponding metadata in your org. This command does not attempt to merge your
+  source with the versions in your org.
 
-  $ sf info releasenotes display
+  To run the command asynchronously, set --wait to 0, which immediately returns the job ID. This way, you can continue
+  to use the CLI. To check the status of the job, use "force source deploy report".
 
-  Display release notes for CLI version 7.120.0:
+  If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of
+  double quotes. On Windows, if the list contains commas, also enclose the entire list in one set of double quotes.
 
-  $ sf info releasenotes display --version 7.120.0
+  If you use the --manifest, --predestructivechanges, or --postdestructivechanges parameters, run the "force source
+  manifest create" command to easily generate the different types of manifest files.
 
-  Display release notes for the CLI version that corresponds to a tag (stable, stable-rc, latest, latest-rc, rc):
+EXAMPLES
+  Deploy the source files in a directory:
 
-  $ sf info releasenotes display --version latest
-```
+    $ sf force source deploy --sourcepath path/to/source
 
-## `sf login`
+  Deploy a specific Apex class and the objects whose source is in a directory:
 
-Log interactively into an environment, such as a Salesforce org.
+    $ sf force source deploy --sourcepath "path/to/apex/classes/MyClass.cls,path/to/source/objects"
 
-```
-USAGE
-  $ sf login
+  Deploy source files in a comma-separated list that contains spaces:
 
-DESCRIPTION
-  Log interactively into an environment, such as a Salesforce org.
+    $ sf force source deploy --sourcepath "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, \
+      path/to/apex/classes"
 
-  Logging into an environment authorizes the CLI to run other commands that connect to that environment, such as
-  deploying or retrieving metadata to and from an org.
+  Deploy all Apex classes:
 
-  The command first prompts you to choose an environment from a list of available ones. It then opens a browser to the
-  appropriate login URL, such as https://login.salesforce.com for an org. Then, depending on the environment you choose,
-  the command prompts for other actions, such as giving the environment an alias or setting it as your default.
+    $ sf force source deploy --metadata ApexClass
 
-  This command is fully interactive and has no flags other than displaying the command-line help. Each environment has
-  its own specific login command, such as "sf login org", which usually provide more flags than this interactive one.
-  For more information about the interactive prompts from this command, see the help for the environment-specific
-  command, such as "sf login org --help".
+  Deploy a specific Apex class:
 
-EXAMPLES
-  Log in interactively:
+    $ sf force source deploy --metadata ApexClass:MyApexClass
 
-    $ sf login
-```
+  Deploy a specific Apex class and update source tracking files :
 
-_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v1.1.2/src/commands/login.ts)_
+    $ sf force source deploy --metadata ApexClass:MyApexClass --tracksource
 
-## `sf login functions`
+  Deploy all custom objects and Apex classes:
 
-Log in to Salesforce Functions.
+    $ sf force source deploy --metadata "CustomObject,ApexClass"
 
-```
-USAGE
-  $ sf login functions
+  Deploy all Apex classes and two specific profiles (one of which has a space in its name):
 
-DESCRIPTION
-  Log in to Salesforce Functions.
+    $ sf force source deploy --metadata "ApexClass, Profile:My Profile, Profile: AnotherProfile"
 
-  This step is required to develop or deploy Salesforce Functions.
+  Deploy all components listed in a manifest:
 
-EXAMPLES
-  Log in to Salesforce Functions:
+    $ sf force source deploy --manifest path/to/package.xml
 
-    $ sf login functions
-```
+  Run the tests that aren’t in any managed packages as part of a deployment:
 
-## `sf login functions jwt`
+    $ sf force source deploy --metadata ApexClass --testlevel RunLocalTests
 
-Login using JWT instead of default web-based flow. This will authenticate you with both sf and Salesforce Functions.
+  Check whether a deployment would succeed (to prepare for Quick Deploy):
 
-```
-USAGE
-  $ sf login functions jwt -u <value> -f <value> -i <value> [--json] [-l <value> | ] [-a <value>] [-d] [-v]
+    $ sf force source deploy --metadata ApexClass --testlevel RunAllTestsInOrg -c
 
-FLAGS
-  -a, --alias=<value>         Alias for the org.
-  -d, --set-default           Set the org as the default that all org-related commands run against.
-  -f, --keyfile=<value>       (required) Path to JWT keyfile.
-  -i, --clientid=<value>      (required) OAuth client ID.
-  -l, --instance-url=<value>  The login URL of the instance the org lives on.
-  -u, --username=<value>      (required) Authentication username.
-  -v, --set-default-dev-hub   Set the org as the default Dev Hub for scratch org creation.
+  Deploy an already validated deployment (Quick Deploy):
 
-GLOBAL FLAGS
-  --json  Format output as json.
+    $ sf force source deploy --validateddeployrequestid 0Af9A00000FTM6pSAH`
 
-DESCRIPTION
-  Login using JWT instead of default web-based flow. This will authenticate you with both sf and Salesforce Functions.
+  Run a destructive operation before the deploy occurs:
 
-  Use this command when executing from a script.
+    $ sf force source deploy --manifest package.xml --predestructivechanges destructiveChangesPre.xml
 
-EXAMPLES
-  Log in using JWT:
+  Run a destructive operation after the deploy occurs:
 
-    $ sf login functions jwt --username example@username.org --keyfile file.key --clientid 123456
+    $ sf force source deploy --manifest package.xml --postdestructivechanges destructiveChangesPost.xml
 
-  Log in and specify the org alias and URL, set as default org and default Dev Hub, and format output as JSON:
+FLAG DESCRIPTIONS
+  -c, --checkonly  Validate the deployed metadata and run all Apex tests, but don't save to the org.
 
-    $ sf login functions jwt --username example@username.org --keyfile file.key --clientid 123456 --alias org-alias \
-      --set-default --set-default-dev-hub --instance-url https://path/to/instance --json
-```
+    IMPORTANT: Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained
+    certain terms to avoid any effect on customer implementations.
 
-## `sf login org`
+    If you change a field type from Master-Detail to Lookup or vice versa, that change isn’t supported when using the
+    --checkonly parameter to test a deployment (validation). This kind of change isn’t supported for test deployments to
+    avoid the risk of data loss or corruption. If a change that isn’t supported for test deployments is included in a
+    deployment package, the test deployment fails and issues an error.
 
-Log in to a Salesforce org using the web server flow.
+    If your deployment package changes a field type from Master-Detail to Lookup or vice versa, you can still validate
+    the changes prior to deploying to Production by performing a full deployment to another test Sandbox. A full
+    deployment includes a validation of the changes as part of the deployment process.
 
-```
-USAGE
-  $ sf login org [--json] [-a <value>] [-b <value>] [-i <value>] [-l <value>] [-d] [-v]
+    Note: A Metadata API deployment that includes Master-Detail relationships deletes all detail records in the Recycle
+    Bin in the following cases.
 
-FLAGS
-  -a, --alias=<value>         Alias for the org.
-  -b, --browser=<value>       Browser in which to open the org.
-  -d, --set-default           Set the org as the default that all org-related commands run against.
-  -i, --clientid=<value>      OAuth client id (also called consumer key) of your custom connected app.
-  -l, --instance-url=<value>  [default: https://login.salesforce.com] URL of the instance that the org lives on.
-                              (defaults to https://login.salesforce.com)
-  -v, --set-default-dev-hub   Set the org as the default Dev Hub for scratch org creation.
+    1. For a deployment with a new Master-Detail field, soft delete (send to the Recycle Bin) all detail records before
+    proceeding to deploy the Master-Detail field, or the deployment fails. During the deployment, detail records are
+    permanently deleted from the Recycle Bin and cannot be recovered.
 
-GLOBAL FLAGS
-  --json  Format output as json.
+    2. For a deployment that converts a Lookup field relationship to a Master-Detail relationship, detail records must
+    reference a master record or be soft-deleted (sent to the Recycle Bin) for the deployment to succeed. However, a
+    successful deployment permanently deletes any detail records in the Recycle Bin.
 
-DESCRIPTION
-  Log in to a Salesforce org using the web server flow.
+  -g, --ignorewarnings  Allow a deployment to complete successfully even if there are warnings.
 
-  Opens a Salesforce instance URL in a web browser so you can enter your credentials and log in to your org. After you
-  log in, you can close the browser window.
+    If a warning occurs and ignoreWarnings is set to true, the success field in DeployMessage is true. When
+    ignoreWarnings is set to false, success is set to false, and the warning is treated like an error.
 
-  Logging into an org authorizes the CLI to run other commands that connect to that org, such as deploying or retrieving
-  a project. You can log into many types of orgs, such as sandboxes, Dev Hubs, Env Hubs, production orgs, and scratch
-  orgs.
+  -l, --testlevel=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg  Deployment testing level.
 
-  We recommend that you set an alias when you log into an org. Aliases make it easy to later reference this org when
-  running commands that require it. If you don’t set an alias, you use the username that you specified when you logged
-  in to the org. If you run multiple commands that reference the same org, consider setting the org as your default. Use
-  --set-default for your default scratch org or sandbox, or --set-default-dev-hub for your default Dev Hub.
+    Valid values are:
 
-  By default, this command uses the global out-of-the-box connected app in your org. If you need more security or
-  control, such as setting the refresh token timeout or specifying IP ranges, create your own connected app using a
-  digital certificate. Make note of the consumer key (also called cliend id) that’s generated for you. Then specify the
-  consumer key with the --clientid flag.
+    - NoTestRun—No tests are run. This test level applies only to deployments to development environments, such as
+    sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.
 
-EXAMPLES
-  Run the command with no flags to open the default Salesforce login page (https://login.salesforce.com):
+    - RunSpecifiedTests—Runs only the tests that you specify in the --runtests option. Code coverage requirements differ
+    from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75%
+    code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
+    trigger individually and is different than the overall coverage percentage.
 
-    $ sf login org
+    - RunLocalTests—All tests in your org are run, except the ones that originate from installed managed and unlocked
+    packages. This test level is the default for production deployments that include Apex classes or triggers.
 
-  Log in to your Dev Hub, set it as your default Dev Hub, and set an alias that you reference later when you create a
-  scratch org:
+    - RunAllTestsInOrg—All tests in your org are run, including tests of managed packages.
 
-    $ sf login org --set-default-dev-hub --alias dev-hub
+    If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more
+    information, see “Running Tests in a Deployment” in the Metadata API Developer Guide.
 
-  Log in to a sandbox and set it as your default org:
+  -m, --metadata=<value>...  Comma-separated list of metadata component names.
 
-    $ sf login org --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com --set-default
+    If you specify this parameter, don’t specify --manifest or --sourcepath.
 
-  Use --browser to specify a specific browser, such as Google Chrome:
+  -o, --ignoreerrors  Ignore any errors and don't roll back deployment.
 
-    $ sf login org --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com --set-default \
-      --browser chrome
+    Keep this parameter set to false when deploying to a production org. If set to true, components without errors are
+    deployed, and components with errors are skipped.
 
-  Use your own connected app by specifying its consumer key (also called client ID):
+  -p, --sourcepath=<value>...  Comma-separated list of source file paths to deploy.
 
-    $ sf login org --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com --set-default \
-      --browser chrome --clientid 04580y4051234051
+    The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all metadata types in the directory and its sub-directories).
 
-FLAG DESCRIPTIONS
-  -b, --browser=<value>  Browser in which to open the org.
+    If you specify this parameter, don’t specify --manifest or --metadata.
 
-    You can log in to an org with one of the following browsers: Firefox, Safari, Google Chrome, or Windows Edge. If you
-    don’t specify --browser, the command uses your default browser. The exact names of the browser applications differ
-    depending on the operating system you're on; check your documentation for details.
+  -q, --validateddeployrequestid=<value>  Deploy request ID of the validated deployment to run a Quick Deploy.
 
-  -l, --instance-url=<value>  URL of the instance that the org lives on. (defaults to https://login.salesforce.com)
+    Deploying a validation helps you shorten your deployment time because tests aren’t rerun. If you have a recent
+    successful validation, you can deploy the validated components without running tests. A validation doesn’t save any
+    components in the org. You use a validation only to check the success or failure messages that you would receive
+    with an actual deployment. To validate your components, add the -c | --checkonly flag when you run "force mdapi
+    deploy". This flag sets the checkOnly="true" parameter for your deployment. Before deploying a recent validation,
+    ensure that the following requirements are met:
 
-    If you specify --instance-url, the value overrides the sfdcLoginUrl value in your sfdx-project.json file.
+    1. The components have been validated successfully for the target environment within the last 10 days.
 
-    To specify a My Domain URL, use the format https://yourcompanyname.my.salesforce.com.
+    2. As part of the validation, Apex tests in the target org have passed.
 
-    To specify a sandbox, set --instance-url to https://MyDomainName--SandboxName.sandbox.my.salesforce.com.
+    3. Code coverage requirements are met.
 
-CONFIGURATION VARIABLES
-  apiVersion   API version of your project. Default: API version of your Dev Hub org. (sfdx only)
-  instanceUrl  URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com. (sfdx only)
+    * If all tests in the org or all local tests are run, overall code coverage is at least 75%, and Apex triggers have
+    some coverage.
 
-ENVIRONMENT VARIABLES
-  SF_INSTANCE_URL  URL of the Salesforce instance that is hosting your org. Default value is
-                     https://login.salesforce.com. Overrides the instanceUrl configuration value.
+    * If specific tests are run with the RunSpecifiedTests test level, each class and trigger that was deployed is
+    covered by at least 75% individually.
+
+  -t, --tracksource  If the deploy succeeds, update source tracking information.
+
+    Doesn't delete locally deleted files from org unless you also specify --predestructivechanges or
+    --postdestructivechanges.
+
+  -w, --wait=<value>  Wait time for command to finish in minutes.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
+
+  -x, --manifest=<value>  Complete path for the manifest (package.xml) file that specifies the components to deploy.
+
+    All child components are included.
+
+    If you specify this parameter, don’t specify --metadata or --sourcepath.
 ```
 
-## `sf login org jwt`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/deploy.ts)_
 
-Log in to a Salesforce org using a JSON web token (JWT).
+## `sf force source deploy cancel`
+
+Cancel a source deployment.
 
 ```
 USAGE
-  $ sf login org jwt [--json] [-a <value>] [-l <value>] [-f <value> -u <value> -i <value>] [-d] [-v]
+  $ sf force source deploy cancel -o <value> [--json] [--api-version <value>] [-w <value>] [-i <value>]
 
 FLAGS
-  -a, --alias=<value>         Alias for the org.
-  -d, --set-default           Set the org as the default that all org-related commands run against.
-  -f, --keyfile=<value>       Path to a file containing the private key.
-  -i, --clientid=<value>      OAuth client id (also called consumer key) of your custom connected app.
-  -l, --instance-url=<value>  [default: https://login.salesforce.com] URL of the instance that the org lives on.
-  -u, --username=<value>      Username of the user logging in.
-  -v, --set-default-dev-hub   Set the org as the default Dev Hub for scratch org creation.
+  -i, --jobid=<value>       Job ID of the deployment you want to cancel; defaults to your most recent CLI deployment if
+                            not specified.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -w, --wait=<value>        [default: [object Object]] Number of minutes to wait for the command to complete and display
+                            results.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Log in to a Salesforce org using a JSON web token (JWT).
-
-  Use this command in automated environments where you can’t interactively log in with a browser, such as in CI/CD
-  scripts.
-
-  Logging into an org authorizes the CLI to run other commands that connect to that org, such as deploying or retrieving
-  a project. You can log into many types of orgs, such as sandboxes, Dev Hubs, Env Hubs, production orgs, and scratch
-  orgs.
-
-  Complete these steps before you run this command:
-
-  1. Create a digital certificate (also called digital signature) and the private key to sign the certificate. You can
-  use your own key and certificate issued by a certification authority. Or use OpenSSL to create a key and a self-signed
-  digital certificate.
+  Cancel a source deployment.
 
-  2. Store the private key in a file on your computer. When you run this command, you set the --keyfile flag to this
-  file.
-
-  3. Create a custom connected app in your org using the digital certificate. Make note of the consumer key (also called
-  client id) that’s generated for you. Be sure the username of the user logging in is approved to use the connected app.
-  When you run this command, you set the --clientid flag to the consumer key.
+  Use this command to cancel a specified asynchronous source deployment. You can also specify a wait time (in minutes)
+  to check for updates to the canceled deploy status.
 
-  See https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_jwt_flow.htm for more
-  information.
-
-  We recommend that you set an alias when you log into an org. Aliases make it easy to later reference this org when
-  running commands that require it. If you don’t set an alias, you use the username that you specified when you logged
-  in to the org. If you run multiple commands that reference the same org, consider setting the org as your default. Use
-  --set-default for your default scratch org or sandbox, or --set-default-dev-hub for your default Dev Hub.
+  To run the command asynchronously, set --wait to 0, which immediately returns the job ID. This way, you can continue
+  to use the CLI. To check the status of the job, use "force source deploy report".
 
 EXAMPLES
-  Log into an org with username jdoe@example.org and on the default instance URL (https://login.salesforce.org). The
-  private key is stored in the file /Users/jdoe/JWT/server.key and the command uses the connected app with consumer
-  key (client id) 04580y4051234051.
+  Cancel a deployment and wait two minutes:
 
-    $ sf login org jwt --username jdoe@example.org --keyfile /Users/jdoe/JWT/server.key --clientid 04580y4051234051
+    $ sf force source deploy cancel --wait 2
 
-  Set the org as the default and give it an alias:
+  If you have multiple deployments in progress and want to cancel a specific one, specify the job ID:
 
-    $ sf login org jwt --username jdoe@example.org --keyfile /Users/jdoe/JWT/server.key --clientid 04580y4051234051 \
-      --alias ci-org --set-default
+    $ sf force source deploy cancel --jobid <jobid>
 
-  Set the org as the default Dev Hub and give it an alias:
+FLAG DESCRIPTIONS
+  -w, --wait=<value>  Number of minutes to wait for the command to complete and display results.
 
-    $ sf login org jwt --username jdoe@example.org --keyfile /Users/jdoe/JWT/server.key --clientid 04580y4051234051 \
-      --alias ci-dev-hub --set-default-dev-hub
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
+```
 
-  Log in to a sandbox using URL https://MyDomainName--SandboxName.sandbox.my.salesforce.com:
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/deploy/cancel.ts)_
 
-    $ sf login org jwt --username jdoe@example.org --keyfile /Users/jdoe/JWT/server.key --clientid 04580y4051234051 \
-      --alias ci-org --set-default --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com
+## `sf force source deploy report`
 
-FLAG DESCRIPTIONS
-  -l, --instance-url=<value>  URL of the instance that the org lives on.
+Check the status of a metadata deployment.
 
-    If you specify an --instance-url value, this value overrides the sfdcLoginUrl value in your sfdx-project.json file.
+```
+USAGE
+  $ sf force source deploy report -o <value> [--json] [--api-version <value>] [-w <value>] [-i <value>] [--verbose]
+    [--resultsdir <value>] [--coverageformatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit]
 
-    To specify a My Domain URL, use the format https://yourcompanyname.my.salesforce.com.
+FLAGS
+  -i, --jobid=<value>
+      Job ID of the deployment you want to check; defaults to your most recent CLI deployment.
 
-    To specify a sandbox, set --instance-url to https://MyDomainName--SandboxName.sandbox.my.salesforce.com.
+  -o, --target-org=<value>
+      (required) Username or alias of the target org.
 
-CONFIGURATION VARIABLES
-  apiVersion   API version of your project. Default: API version of your Dev Hub org. (sfdx only)
-  instanceUrl  URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com. (sfdx only)
+  -w, --wait=<value>
+      [default: [object Object]] Number of minutes to wait for the command to complete and display results to the terminal
+      window.
 
-ENVIRONMENT VARIABLES
-  SF_INSTANCE_URL  URL of the Salesforce instance that is hosting your org. Default value is
-                     https://login.salesforce.com. Overrides the instanceUrl configuration value.
-```
+  --api-version=<value>
+      Override the api version used for api requests made by this command
 
-## `sf logout`
+  --coverageformatters=clover,cobertura,html-spa,html,json,json-summary,lcovonly,none,teamcity,text,text-summary...
+      Format of the code coverage results.
 
-Log out interactively from environments, such as Salesforce orgs and compute environments.
+  --junit
+      Output JUnit test results.
 
-```
-USAGE
-  $ sf logout [--json] [--no-prompt]
+  --resultsdir=<value>
+      Output directory for code coverage and JUnit results; defaults to the deploy ID.
 
-FLAGS
-  --no-prompt  Don't prompt for confirmation; logs you out of all environments.
+  --verbose
+      Verbose output of deploy result.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Log out interactively from environments, such as Salesforce orgs and compute environments.
+  Check the status of a metadata deployment.
 
-  By default, the command prompts you to select which environments you want to log out of. Use --no-prompt to not be
-  prompted and log out of all environments.
-
-  Be careful! If you log out of a scratch org without having access to its password, you can't access the scratch org
-  again, either through the CLI or the Salesforce UI.
+  Specify the job ID for the deploy you want to check. You can also specify a wait time (minutes) to check for updates
+  to the deploy status.
 
 EXAMPLES
-  Interactively select the environments to log out of:
+  Check the status of the most recent deployment on your default org:
 
-    $ sf logout
+    $ sf force source deploy report
 
-  Log out of all environments, without being prompted:
+  Check the status using the job ID; output JUnit test results and format code coverage results in the specified
+  format:
 
-    $ sf logout --no-prompt
+    $ sf force source deploy report --jobid <id> --junit --coverageformatters cobertura
+
+FLAG DESCRIPTIONS
+  -w, --wait=<value>  Number of minutes to wait for the command to complete and display results to the terminal window.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
 ```
 
-_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/v1.1.2/src/commands/logout.ts)_
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/deploy/report.ts)_
 
-## `sf logout functions`
+## `sf force source pull`
 
-Log out of your Salesforce Functions account.
+Pull changed source from the org to your project to keep them in sync.
 
 ```
 USAGE
-  $ sf logout functions [--json]
+  $ sf force source pull -o <value> [--json] [--verbose] [--api-version <value>] [-f] [-w <value>]
+
+FLAGS
+  -f, --forceoverwrite      Ignore conflict warnings; changes in the org overwrite changes in the project.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -w, --wait=<value>        [default: [object Object]] Number of minutes to wait for the command to complete and display
+                            results to the terminal window.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --verbose                 Display additional details about the command results.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
+DESCRIPTION
+  Pull changed source from the org to your project to keep them in sync.
+
+  If the command detects a conflict, it displays the conflicts but does not complete the process. After reviewing the
+  conflict, rerun the command with the --forceoverwrite parameter.
+
 EXAMPLES
-  Log out:
+  Pull source from your default org:
+
+    $ sf force source pull
 
-    $ sf logout functions
+  Pull source from the org with alias "myscratch"; ignore any conflicts and overwrite the local project files with org
+  changes; wait for only 5 minutes:
+
+    $ sf force source pull --target-org myscratch --wait 5 --forceoverwrite
+
+FLAG DESCRIPTIONS
+  -w, --wait=<value>  Number of minutes to wait for the command to complete and display results to the terminal window.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
 ```
 
-## `sf logout org`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/pull.ts)_
 
-Log out of a specified Salesforce org.
+## `sf force source push`
+
+Push changed source from your project to an org to keep them in sync.
 
 ```
 USAGE
-  $ sf logout org -o <value> [--json] [--no-prompt]
+  $ sf force source push -o <value> [--json] [--api-version <value>] [-f] [-w <value>] [-g] [--quiet]
 
 FLAGS
-  -o, --target-org=<value>  (required) Org alias or username to log out of.
-  --no-prompt               Don't prompt for confirmation.
+  -f, --forceoverwrite      Ignore conflict warnings and push source anyway; changes in the project overwrite changes in
+                            the org.
+  -g, --ignorewarnings      Deploy changes even if warnings are generated.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -w, --wait=<value>        [default: [object Object]] Number of minutes to wait for the command to complete and display
+                            results to the terminal window.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --quiet                   Minimize JSON and sdtout output on success.
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Log out of a specified Salesforce org.
-
-  By default, the command prompts you to confirm that you want to log out of the specified org. Use --no-prompt to not
-  be prompted.
+  Push changed source from your project to an org to keep them in sync.
 
-  Be careful! If you log out of a scratch org without having access to its password, you can't access the scratch org
-  again, either through the CLI or the Salesforce UI.
+  If the command detects a conflict, it displays the conflicts but does not complete the process. After reviewing the
+  conflict, rerun the command with the --forceoverwrite parameter.
 
 EXAMPLES
-  Log out of an org with alias "ci-org":
+  Push source to your default org:
 
-    $ sf logout org --target-org ci-org
+    $ sf force source push
 
-  If your org doesn’t have an alias, specify the username that you used when you logged into it:
+  Push source to the org with alias "myscratch"; ignore any conflicts and overwrite with org with the local project
+  changes; wait for only 5 minutes:
 
-    $ sf logout org --target-org jdoe@example.org
+    $ sf force source push --target-org myscratch --wait 5 --forceoverwrite
 
-CONFIGURATION VARIABLES
-  apiVersion   API version of your project. Default: API version of your Dev Hub org. (sfdx only)
-  instanceUrl  URL of the Salesforce instance hosting your org. Default: https://login.salesforce.com. (sfdx only)
-  target-org   Username or alias of the org that all commands run against by default. (sf only)
+FLAG DESCRIPTIONS
+  -w, --wait=<value>  Number of minutes to wait for the command to complete and display results to the terminal window.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
 ```
 
-## `sf plugins`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/push.ts)_
 
-List installed plugins.
+## `sf force source retrieve`
+
+Retrieve source from an org.
 
 ```
 USAGE
-  $ sf plugins [--core]
+  $ sf force source retrieve -o <value> [--json] [-a <value>] [-r <value> | -n <value> | -p <value>] [-w <value>] [-x
+    <value> | -m <value> | ] [-f -t] [--verbose]
 
 FLAGS
-  --core  Show core plugins.
+  -a, --api-version=<value>        Override the api version used for api requests made by this command
+  -f, --forceoverwrite             Ignore conflict warnings and overwrite changes to the project.
+  -m, --metadata=<value>...        Comma-separated list of names of metadata components to retrieve from the org.
+  -n, --packagenames=<value>...    Comma-separated list of packages to retrieve.
+  -o, --target-org=<value>         (required) Username or alias of the target org.
+  -p, --sourcepath=<value>...      Comma-separated list of file paths for source to retrieve from the org.
+  -r, --retrievetargetdir=<value>  Root of the directory structure into which the source files are retrieved.
+  -t, --tracksource                If the retrieve succeeds, update source tracking information; doesn't delete local
+                                   files that were deleted in the org.
+  -w, --wait=<value>               [default: [object Object]] Number of minutes to wait for the command to complete and
+                                   display results to the terminal window.
+  -x, --manifest=<value>           Complete path for the manifest (package.xml) file that specifies the components to
+                                   retrieve.
+  --verbose                        Verbose output of retrieve result.
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  List installed plugins.
+  Retrieve source from an org.
+
+  Use this command to retrieve source (metadata that’s in source format) from an org. To take advantage of change
+  tracking with scratch orgs, use "force source pull". To retrieve metadata that’s in metadata format, use "force mdapi
+  retrieve".
+
+  The source you retrieve overwrites the corresponding source files in your local project. This command does not attempt
+  to merge the source from your org with your local source files.
+
+  If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of
+  double quotes. On Windows, if the list contains commas, also enclose it in one set of double quotes.
 
 EXAMPLES
-  $ sf plugins
-```
+  Retrieve the source files in a directory from your default org:
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v2.1.0/src/commands/plugins/index.ts)_
+    $ sf force source retrieve --sourcepath path/to/source
 
-## `sf plugins:install PLUGIN...`
+  Retrieve a specific Apex class and the objects whose source is in a directory from an org with alias "myscratch":
 
-Installs a plugin into the CLI.
+    $ sf force source retrieve --sourcepath "path/to/apex/classes/MyClass.cls,path/to/source/objects" --target-org \
+      myscratch
 
-```
-USAGE
-  $ sf plugins:install PLUGIN...
+  Retrieve source files in a comma-separated list that contains spaces:
 
-ARGUMENTS
-  PLUGIN  Plugin to install.
+    $ sf force source retrieve --sourcepath "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, \
+      path/to/apex/classes"
 
-FLAGS
-  -f, --force    Run yarn install with force flag.
-  -h, --help     Show CLI help.
-  -v, --verbose
+  Retrieve all Apex classes:
 
-DESCRIPTION
-  Installs a plugin into the CLI.
+    $ sf force source retrieve --metadata ApexClass
 
-  Can be installed from npm or a git url.
+  Retrieve a specific Apex class:
 
-  Installation of a user-installed plugin will override a core plugin.
+    $ sf force source retrieve --metadata ApexClass:MyApexClass
 
-  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
-  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
-  the CLI without the need to patch and update the whole CLI.
+  Retrieve a specific Apex class and update source tracking files:
 
-ALIASES
-  $ sf plugins add
+    $ sf force source retrieve --metadata ApexClass:MyApexClass --tracksource
 
-EXAMPLES
-  $ sf plugins:install myplugin
+  Retrieve all custom objects and Apex classes:
 
-  $ sf plugins:install https://github.com/someuser/someplugin
+    $ sf force source retrieve --metadata "CustomObject,ApexClass"
 
-  $ sf plugins:install someuser/someplugin
-```
+  Retrieve all Apex classes and two specific profiles (one of which has a space in its name):
 
-## `sf plugins:inspect PLUGIN...`
+    $ sf force source retrieve --metadata "ApexClass, Profile:My Profile, Profile: AnotherProfile"
 
-Displays installation properties of a plugin.
+  Retrieve all metadata components listed in a manifest:
 
-```
-USAGE
-  $ sf plugins:inspect PLUGIN...
+    $ sf force source retrieve --manifest path/to/package.xml
 
-ARGUMENTS
-  PLUGIN  [default: .] Plugin to inspect.
+  Retrieve metadata from a package or multiple packages:
 
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
+    $ sf force source retrieve --packagenames MyPackageName
+    $ sf force source retrieve --packagenames "Package1, PackageName With Spaces, Package3"
 
-DESCRIPTION
-  Displays installation properties of a plugin.
+  Retrieve all metadata from a package and specific components that aren’t in the package, specify both -n |
+  --packagenames and one other scoping parameter:
 
-EXAMPLES
-  $ sf plugins:inspect myplugin
-```
+    $ sf force source retrieve --packagenames MyPackageName --sourcepath path/to/apex/classes
+    $ sf force source retrieve --packagenames MyPackageName --metadata ApexClass:MyApexClass
+    $ sf force source retrieve --packagenames MyPackageName --manifest path/to/package.xml
 
-## `sf plugins:install PLUGIN...`
+  Retrieve source files to a given directory instead of the default package directory specified in sfdx-project.json:
 
-Installs a plugin into the CLI.
+    $ sf force source retrieve --metadata "StandardValueSet:TaskStatus" --retrievetargetdir path/to/unpackaged
 
-```
-USAGE
-  $ sf plugins:install PLUGIN...
+FLAG DESCRIPTIONS
+  -m, --metadata=<value>...  Comma-separated list of names of metadata components to retrieve from the org.
 
-ARGUMENTS
-  PLUGIN  Plugin to install.
+    If you specify this parameter, don’t specify --manifest or --sourcepath.
 
-FLAGS
-  -f, --force    Run yarn install with force flag.
-  -h, --help     Show CLI help.
-  -v, --verbose
+  -p, --sourcepath=<value>...  Comma-separated list of file paths for source to retrieve from the org.
 
-DESCRIPTION
-  Installs a plugin into the CLI.
+    The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all source files in the directory and its sub-directories).
 
-  Can be installed from npm or a git url.
+    If you specify this parameter, don’t specify --manifest or --metadata.
 
-  Installation of a user-installed plugin will override a core plugin.
+  -r, --retrievetargetdir=<value>  Root of the directory structure into which the source files are retrieved.
 
-  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
-  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
-  the CLI without the need to patch and update the whole CLI.
+    If the target directory matches one of the package directories in your sfdx-project.json file, the command fails.
 
-ALIASES
-  $ sf plugins add
+    Running the command multiple times with the same target adds new files and overwrites existing files.
 
-EXAMPLES
-  $ sf plugins:install myplugin
+  -w, --wait=<value>  Number of minutes to wait for the command to complete and display results to the terminal window.
 
-  $ sf plugins:install https://github.com/someuser/someplugin
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
 
-  $ sf plugins:install someuser/someplugin
+  -x, --manifest=<value>  Complete path for the manifest (package.xml) file that specifies the components to retrieve.
+
+    If you specify this parameter, don’t specify --metadata or --sourcepath.
 ```
 
-## `sf plugins:link PLUGIN`
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/retrieve.ts)_
 
-Links a plugin into the CLI for development.
+## `sf force source status`
+
+List changes that have been made locally, in an org, or both.
 
 ```
 USAGE
-  $ sf plugins:link PLUGIN
+  $ sf force source status -o <value> [--json] [--api-version <value>] [-l | -r] [--concise]
 
-ARGUMENTS
-  PATH  [default: .] path to plugin
+FLAGS
+  -l, --local               List the changes that have been made locally.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -r, --remote              List the changes that have been made in the org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --concise                 Show only the changes that will be pushed or pulled; omits files that are forceignored.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+EXAMPLES
+  List changes that have been made locally but not in the org with alias "myscratch":
+
+    $ sf force source status --local --target-org myscratch
+
+  List changes that have been made in your default org but aren't reflected in your local project:
+
+    $ sf force source status --remote
+```
+
+_See code: [@salesforce/plugin-source](https://github.com/salesforcecli/plugin-source/blob/2.10.37/src/commands/force/source/status.ts)_
+
+## `sf force user password generate`
+
+Generate a random password for scratch org users.
+
+```
+USAGE
+  $ sf force user password generate -u <value> [--json] [-o <value>] [-l <value>] [-c <value>] [--api-version <value>]
 
 FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
+  -c, --complexity=<value>       [default: 5] Level of password complexity or strength; the higher the value, the
+                                 stronger the password.
+  -l, --length=<value>           [default: 13] Number of characters in the generated password; valid values are between
+                                 8 and 100.
+  -o, --on-behalf-of=<value>...  Comma-separated list of usernames or aliases to assign the password to.
+  -u, --target-org=<value>       (required) Scratch org alias or login user.
+  --api-version=<value>          Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Links a plugin into the CLI for development.
+  Generate a random password for scratch org users.
 
-  Installation of a linked plugin will override a user-installed or core plugin.
+  By default, new scratch orgs contain one admin user with no password. Use this command to generate or change a
+  password for any scratch org user. After it's set, you can’t unset a password, you can only change it.
 
-  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
-  command will override the user-installed or core plugin implementation. This is useful for development work.
+  To change the password strength, set the --complexity flag to a value between 0 and 5. Each value specifies the types
+  of characters used in the generated password:
+
+  0 - lower case letters only
+  1 - lower case letters and numbers only
+  2 - lower case letters and symbols only
+  3 - lower and upper case letters and numbers only
+  4 - lower and upper case letters and symbols only
+  5 - lower and upper case letters and numbers and symbols only
+
+  To see a password that was previously generated, run "org display user".
 
 EXAMPLES
-  $ sf plugins:link myplugin
+  Generate a password for the original admin user of your default scratch org:
+
+    $ sf force user password generate
+
+  Generate a password that contains 12 characters for the original admin user of the scratch org with alias
+  "my-scratch":
+
+    $ sf force user password generate --length 12 --target-org my-scratch
+
+  Generate a password for your default scratch org admin user that uses lower and upper case letters and numbers only:
+
+    $ sf force user password generate --complexity 3
+
+  Generate a password for the specified users in the default scratch org:
+
+    $ sf force user password generate --on-behalf-of user1@my.org --on-behalf-of user2@my.org --on-behalf-of \
+      user3@my.org
 ```
 
-## `sf plugins:uninstall PLUGIN...`
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/force/user/password/generate.ts)_
 
-Removes a plugin from the CLI.
+## `sf help [COMMANDS]`
+
+Display help for sf.
 
 ```
 USAGE
-  $ sf plugins:uninstall PLUGIN...
+  $ sf help [COMMANDS] [-n]
 
 ARGUMENTS
-  PLUGIN  plugin to uninstall
+  COMMANDS  Command to show help for.
 
 FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
+  -n, --nested-commands  Include all nested commands in the output.
 
 DESCRIPTION
-  Removes a plugin from the CLI.
+  Display help for sf.
+```
+
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/5.2.20/src/commands/help.ts)_
+
+## `sf info releasenotes display`
+
+Display Salesforce CLI release notes on the command line.
+
+```
+USAGE
+  $ sf info releasenotes display [--json] [-v <value>]
+
+FLAGS
+  -v, --version=<value>  CLI version or tag for which to display release notes.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Display Salesforce CLI release notes on the command line.
+
+  By default, this command displays release notes for the currently installed CLI version on your computer. Use the
+  --version flag to view release notes for a different release.
 
 ALIASES
-  $ sf plugins unlink
-  $ sf plugins remove
+  $ sf whatsnew
+
+EXAMPLES
+  Display release notes for the currently installed CLI version:
+
+    $ sf info releasenotes display stable, stable-rc, latest, latest-rc, rc
+
+  Display release notes for CLI version 7.120.0:
+
+    $ sf info releasenotes display --version 7.120.0 stable, stable-rc, latest, latest-rc, rc
+
+  Display release notes for the CLI version that corresponds to a tag (stable, stable-rc, latest, latest-rc, rc):
+
+    $ sf info releasenotes display --version latest
 ```
 
-## `sf plugins:trust:verify -n <string> [-r <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`
+_See code: [@salesforce/plugin-info](https://github.com/salesforcecli/plugin-info/blob/2.6.46/src/commands/info/releasenotes/display.ts)_
+
+## `sf lightning generate app`
 
-Validate a digital signature for a npm package.
+Generate a Lightning App.
 
 ```
 USAGE
-  $ sf plugins trust verify -n <string> [-r <string>] [--json] [--loglevel
-    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf lightning generate app -n <value> [--json] [-t DefaultLightningApp] [-d <value>] [--api-version <value>]
 
 FLAGS
-  -n, --npm=<value>                                                                 (required) Specify the npm name.
-                                                                                    This can include a tag/version.
-  -r, --registry=<value>                                                            The registry name. The behavior is
-                                                                                    the same as npm.
-  --json                                                                            format output as json
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated Lightning App.
+  -t, --template=<option>   [default: DefaultLightningApp] Template to use for file creation.
+                            <options: DefaultLightningApp>
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Validate a digital signature for a npm package.
+  Generate a Lightning App.
+
+  Generates a Lightning App bundle in the specified directory or the current working directory. The bundle consists of
+  multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning app create
 
 EXAMPLES
-  $ sf plugins trust verify --npm @scope/npmName --registry http://my.repo.org:4874
+  Generate the metadata files for a Lightning app bundle called "myapp" in the current directory:
 
-  $ sf plugins trust verify --npm @scope/npmName
+    $ sf lightning generate app --name myapp
+
+  Similar to the previous example, but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate app --name myapp --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning App.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningApp  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-## `sf plugins:uninstall PLUGIN...`
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/lightning/generate/app.ts)_
 
-Removes a plugin from the CLI.
+## `sf lightning generate component`
+
+Generate a bundle for an Aura component or a Lightning web component.
 
 ```
 USAGE
-  $ sf plugins:uninstall PLUGIN...
+  $ sf lightning generate component -n <value> [--json] [-t default|analyticsDashboard|analyticsDashboardWithStep] [-d <value>]
+    [--api-version <value>] [--type aura|lwc]
 
-ARGUMENTS
-  PLUGIN  plugin to uninstall
+FLAGS
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated Lightning Component.
+  -t, --template=<option>   [default: default] Template to use for file creation.
+                            <options: default|analyticsDashboard|analyticsDashboardWithStep>
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --type=<option>           [default: aura] Type of the component bundle.
+                            <options: aura|lwc>
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Generate a bundle for an Aura component or a Lightning web component.
+
+  Generates the bundle in the specified directory or the current working directory. The bundle consists of multiple
+  files in a directory with the designated name. Lightning web components are contained in the directory with name
+  "lwc", Aura components in "aura".
+
+  To generate a Lightning web component, pass "--type lwc" to the command. If you don’t specify --type, Salesforce CLI
+  generates an Aura component by default.
+
+ALIASES
+  $ sf force lightning component create
+
+EXAMPLES
+  Generate the metadata files for an Aura component bundle in the current directory:
+
+    $ sf lightning generate component --name mycomponent
+
+  Generate a Lightning web component bundle in the current directory:
+
+    $ sf lightning generate component --name mycomponent --type lwc
+
+  Generate an Aura component bundle in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate component --name mycomponent --output-dir force-app/main/default/aura
+
+  Generate a Lightning web component bundle in the "force-app/main/default/lwc" directory:
+
+    $ sf lightning generate component --name mycomponent --type lwc --output-dir force-app/main/default/lwc
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Component.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=default|analyticsDashboard|analyticsDashboardWithStep  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/lightning/generate/component.ts)_
+
+## `sf lightning generate event`
+
+Generate a Lightning Event.
+
+```
+USAGE
+  $ sf lightning generate event -n <value> [--json] [-t DefaultLightningEvt] [-d <value>] [--api-version <value>]
 
 FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated Lightning Event.
+  -t, --template=<option>   [default: DefaultLightningEvt] Template to use for file creation.
+                            <options: DefaultLightningEvt>
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Removes a plugin from the CLI.
+  Generate a Lightning Event.
+
+  Generates a Lightning Event bundle in the specified directory or the current working directory. The bundle consists of
+  multiple files in a folder with the designated name.
 
 ALIASES
-  $ sf plugins unlink
-  $ sf plugins remove
+  $ sf force lightning event create
+
+EXAMPLES
+  Generate the metadata files for a Lightning event bundle called "myevent" in the current directory:
+
+    $ sf lightning generate event --name myevent
+
+  Similar to previous example, but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate event --name myevent --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Event.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningEvt  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-## `sf plugins:uninstall PLUGIN...`
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/lightning/generate/event.ts)_
 
-Removes a plugin from the CLI.
+## `sf lightning generate interface`
+
+Generate a Lightning Interface.
+
+```
+USAGE
+  $ sf lightning generate interface -n <value> [--json] [-t DefaultLightningIntf] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated Lightning Interface.
+  -t, --template=<option>   [default: DefaultLightningIntf] Template to use for file creation.
+                            <options: DefaultLightningIntf>
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Generate a Lightning Interface.
+
+  Generates a Lightning Interface bundle in the specified directory or the current working directory. The bundle
+  consists of multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning interface create
+
+EXAMPLES
+  Generate the metadata files for a Lightning interface bundle called "myinterface" in the current directory:
+
+    $ sf lightning generate interface --name myinterface
+
+  Similar to the previous example but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate interface --name myinterface --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Interface.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningIntf  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/lightning/generate/interface.ts)_
+
+## `sf lightning generate test`
+
+Generate a Lightning test.
+
+```
+USAGE
+  $ sf lightning generate test -n <value> [--json] [-t DefaultLightningTest] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated Lightning Test.
+  -t, --template=<option>   [default: DefaultLightningTest] Template to use for file creation.
+                            <options: DefaultLightningTest>
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Generate a Lightning test.
+
+  Generates the test in the specified directory or the current working directory. The .resource file and associated
+  metadata file are generated.
+
+ALIASES
+  $ sf force lightning test create
+
+EXAMPLES
+  Generate the metadata files for the Lightning test called MyLightningTest in the current directory:
+
+    $ sf lightning generate test --name MyLightningTest
+
+  Similar to the previous example but generate the files in the "force-app/main/default/lightningTests" directory:
+
+    $ sf lightning generate test --name MyLightningTest --output-dir force-app/main/default/lightningTests
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Test.
+
+    Name of the new Lightning test; can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningTest  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/lightning/generate/test.ts)_
+
+## `sf limits api display`
+
+Display information about limits in your org.
+
+```
+USAGE
+  $ sf limits api display -o <value> [--json] [--api-version <value>]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Display information about limits in your org.
+
+  For each limit, this command returns the maximum allocation and the remaining allocation based on usage. See this
+  topic for a description of each limit:
+  https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_limits.htm.
+
+ALIASES
+  $ sf force limits api display
+  $ sf org list limits
+
+EXAMPLES
+  Display limits in your default org:
+
+    $ sf limits api display
+
+  Display limits in the org with alias "my-scratch-org":
+
+    $ sf limits api display --target-org my-scratch-org
+```
+
+_See code: [@salesforce/plugin-limits](https://github.com/salesforcecli/plugin-limits/blob/2.3.36/src/commands/limits/api/display.ts)_
+
+## `sf limits recordcounts display`
+
+Display record counts for the specified standard or custom objects.
+
+```
+USAGE
+  $ sf limits recordcounts display -o <value> [--json] [-s <value>] [--api-version <value>]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>...  [default: ] API name of the standard or custom object for which to display record counts.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Display record counts for the specified standard or custom objects.
+
+  Use this command to get an approximate count of the records in standard or custom objects in your org. These record
+  counts are the same as the counts listed in the Storage Usage page in the Setup UI. The record counts are approximate
+  because they're calculated asynchronously and your org's storage usage isn't updated immediately. To display all
+  available record counts, run the command without the --sobject flag.
+
+ALIASES
+  $ sf force limits recordcounts display
+  $ sf org list sobject record-counts
+
+EXAMPLES
+  Display all available record counts in your default org:
+
+    $ sf limits recordcounts display
+
+  Display record counts for the Account, Contact, Lead, and Opportunity objects in your default org:
+
+    $ sf limits recordcounts display --sobject Account --sobject Contact --sobject Lead --sobject Opportunity
+
+  Display record counts for the Account and Lead objects for the org with alias "my-scratch-org":
+
+    $ sf limits recordcounts display --sobject Account --sobject Lead --target-org my-scratch-org
+```
+
+_See code: [@salesforce/plugin-limits](https://github.com/salesforcecli/plugin-limits/blob/2.3.36/src/commands/limits/recordcounts/display.ts)_
+
+## `sf login`
+
+Log interactively into an environment.
+
+```
+USAGE
+  $ sf login
+
+DESCRIPTION
+  Log interactively into an environment.
+
+  Logging into an environment authorizes the CLI to run other commands that connect to that environment.
+
+EXAMPLES
+  Log in interactively:
+
+    $ sf login
+```
+
+_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/1.2.32/src/commands/login.ts)_
+
+## `sf logout`
+
+Log out interactively from environments.
+
+```
+USAGE
+  $ sf logout [--json] [--no-prompt]
+
+FLAGS
+  --no-prompt  Don't prompt for confirmation; logs you out of all environments.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Log out interactively from environments.
+
+  By default, the command prompts you to select which environments you want to log out of. Use --no-prompt to not be
+  prompted and log out of all environments.
+
+EXAMPLES
+  Interactively select the environments to log out of:
+
+    $ sf logout
+
+  Log out of all environments, without being prompted:
+
+    $ sf logout --no-prompt
+```
+
+_See code: [@salesforce/plugin-login](https://github.com/salesforcecli/plugin-login/blob/1.2.32/src/commands/logout.ts)_
+
+## `sf org assign permset`
+
+Assign a permission set to one or more users of a scratch org.
+
+```
+USAGE
+  $ sf org assign permset -n <value> -o <value> [--json] [-b <value>] [--api-version <value>]
+
+FLAGS
+  -b, --on-behalf-of=<value>...  Username or alias to assign the permission set to.
+  -n, --name=<value>...          (required) Permission set to assign.
+  -o, --target-org=<value>       (required) Scratch org alias or login user.
+  --api-version=<value>          Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Assign a permission set to one or more users of a scratch org.
+
+  To specify an alias for the --target-org or --on-behalf-of flags, use the CLI username alias, such as the one you set
+  with the "alias set" command. Don't use the value of the Alias field of the User Salesforce object for the org user.
+
+  To assign multiple permission sets, either set multiple --name flags or a single --name flag with multiple names
+  separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to
+  --on-behalf-of.
+
+EXAMPLES
+  Assign two permission sets called DreamHouse and CloudHouse to original admin user of your default scratch org:
+
+    $ sf org assign permset --name DreamHouse --name CloudHouse
+
+  Assign the Dreamhouse permission set to the original admin user of the scratch org with alias "my-scratch":
+
+    $ sf org assign permset --name DreamHouse --target-org my-scratch
+
+  Assign the Dreamhouse permission set to the specified list of users of your default scratch org:
+
+    $ sf org assign permset --name DreamHouse --on-behalf-of user1@my.org --on-behalf-of user2 --on-behalf-of user
+```
+
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/org/assign/permset.ts)_
+
+## `sf org assign permsetlicense`
+
+Assign a permission set license to one or more users of a scratch org.
+
+```
+USAGE
+  $ sf org assign permsetlicense -n <value> -o <value> [--json] [-b <value>] [--api-version <value>]
+
+FLAGS
+  -b, --on-behalf-of=<value>...  Usernames or alias to assign the permission set license to.
+  -n, --name=<value>             (required) Name of the permission set license to assign.
+  -o, --target-org=<value>       (required) Scratch org alias or login user.
+  --api-version=<value>          Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Assign a permission set license to one or more users of a scratch org.
+
+  To specify an alias for the --target-org or --on-behalf-of flags, use the CLI username alias, such as the one you set
+  with the "alias set" command. Don't use the value of the Alias field of the User Salesforce object for the org user.
+
+  To assign multiple permission sets, either set multiple --name flags or a single --name flag with multiple names
+  separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to
+  --on-behalf-of.
+
+EXAMPLES
+  Assign the DreamHouse permission set license to original admin user of your default scratch org:
+
+    $ sf org assign permsetlicense --name DreamHouse
+
+  Assign two permission set licenses to the original admin user of the scratch org with alias "my-scratch":
+
+    $ sf org assign permsetlicense --name DreamHouse --name CloudHouse --target-org my-scratch
+
+  Assign the Dreamhouse permission set license to the specified list of users of your default scratch org:
+
+    $ sf org assign permsetlicense --name DreamHouse --on-behalf-of user1@my.org --on-behalf-of user2 --on-behalf-of \
+      user3
+```
+
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/org/assign/permsetlicense.ts)_
+
+## `sf org create sandbox`
+
+Create a sandbox org.
+
+```
+USAGE
+  $ sf org create sandbox -o <value> [--json] [-f <value> | -n <value> | -l Developer|Developer_Pro|Partial|Full] [-s]
+    [-a <value>] [-w <value> | --async] [-i <value> | ] [-c <value> | ] [--no-prompt] [--no-track-source]
+
+FLAGS
+  -a, --alias=<value>            Alias for the sandbox org.
+  -c, --clone=<value>            Name of the sandbox org to clone.
+  -f, --definition-file=<value>  Path to a sandbox definition file.
+  -i, --poll-interval=<seconds>  [default: [object Object]] Number of seconds to wait between retries.
+  -l, --license-type=<option>    Type of sandbox license.
+                                 <options: Developer|Developer_Pro|Partial|Full>
+  -n, --name=<value>             Name of the sandbox org.
+  -o, --target-org=<value>       (required) Username or alias of the production org that contains the sandbox license.
+  -s, --set-default              Set the sandbox org as your default org.
+  -w, --wait=<minutes>           [default: [object Object]] Number of minutes to wait for the sandbox org to be ready.
+  --async                        Request the sandbox creation, but don't wait for it to complete.
+  --no-prompt                    Don't prompt for confirmation about the sandbox configuration.
+  --no-track-source              Do not use source tracking for this sandbox.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Create a sandbox org.
+
+  There are two ways to create a sandbox org: specify a definition file that contains the sandbox options or use the
+  --name and --license-type flags to specify the two required options. If you want to set an option other than name or
+  license type, such as apexClassId, you must use a definition file.
+
+ALIASES
+  $ sf env create sandbox
+
+EXAMPLES
+  Create a sandbox org using a definition file and give it the alias "MyDevSandbox". The production org that contains
+  the sandbox license has the alias "prodOrg".
+
+    $ sf org create sandbox -f config/dev-sandbox-def.json --alias MyDevSandbox --target-org prodOrg
+
+  Create a sandbox org by directly specifying its name and type of license (Developer) instead of using a definition
+  file. Set the sandbox org as your default.
+
+    $ sf org create sandbox --name mysandbox --license-type Developer --alias MyDevSandbox --target-org prodOrg \
+      --set-default
+
+FLAG DESCRIPTIONS
+  -a, --alias=<value>  Alias for the sandbox org.
+
+    When you create a sandbox, the generated usernames are based on the usernames present in the production org. To
+    ensure uniqueness, the new usernames are appended with the name of the sandbox. For example, the username
+    "user@example.com" in the production org results in the username "user@example.com.mysandbox" in a sandbox named
+    "mysandbox". When you set an alias for a sandbox org, it's assigned to the resulting username of the user running
+    this command.
+
+  -c, --clone=<value>  Name of the sandbox org to clone.
+
+    The value of clone must be an existing sandbox in the same target-org.
+
+  -f, --definition-file=<value>  Path to a sandbox definition file.
+
+    The sandbox definition file is a blueprint for the sandbox. You can create different definition files for each
+    sandbox type that you use in the development process. See
+    <https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_sandbox_definition.htm> for all
+    the options you can specify in the defintion file.
+
+  -n, --name=<value>  Name of the sandbox org.
+
+    The name must be a unique alphanumeric string (10 or fewer characters) to identify the sandbox. You can’t reuse a
+    name while a sandbox is in the process of being deleted.
+
+  -o, --target-org=<value>  Username or alias of the production org that contains the sandbox license.
+
+    When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to
+    the new sandbox org.
+
+  -w, --wait=<minutes>  Number of minutes to wait for the sandbox org to be ready.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays
+    the "sf org resume sandbox" command you run to check the status of the create. The displayed command includes the
+    job ID for the running sandbox creation.
+
+  --async  Request the sandbox creation, but don't wait for it to complete.
+
+    The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue
+    to use the CLI. To check the status of the sandbox creation, run "sf org resume sandbox".
+
+  --no-track-source  Do not use source tracking for this sandbox.
+
+    We recommend you enable source tracking in Developer and Developer Pro sandbox, which is why it's the default
+    behavior. Source tracking allows you to track the changes you make to your metadata, both in your local project and
+    in the sandbox, and to detect any conflicts between the two.
+
+    To disable source tracking in the new sandbox, specify the --no-track-source flag. The main reason to disable source
+    tracking is for performance. For example, while you probably want to deploy metadata and run Apex tests in your
+    CI/CD jobs, you probably don't want to incur the costs of source tracking (checking for conflicts, polling the
+    SourceMember object, various file system operations.) This is a good use case for disabling source tracking in the
+    sandbox.
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/create/sandbox.ts)_
+
+## `sf org create scratch`
+
+Create a scratch org.
+
+```
+USAGE
+  $ sf org create scratch -v <value> [--json] [-a <value>] [--async] [-d] [-f <value>] [-c] [-e
+    developer|enterprise|group|professional|partner-developer|partner-enterprise|partner-group|partner-professional]
+    [-m] [-y <value>] [-w <value>] [--api-version <value>] [-i <value>] [-t] [--username <value>] [--description
+    <value>] [--name <value>] [--release preview|previous] [--admin-email <value>] [--source-org <value>]
+
+FLAGS
+  -a, --alias=<value>            Alias for the scratch org.
+  -d, --set-default              Set the scratch org as your default org
+  -f, --definition-file=<value>  Path to a scratch org definition file.
+  -i, --client-id=<value>        Consumer key of the Dev Hub connected app.
+  -t, --[no-]track-source        Use source tracking for this scratch org. Set --no-track-source to disable source
+                                 tracking.
+  -v, --target-dev-hub=<value>   (required) Username or alias of the Dev Hub org.
+  -w, --wait=<minutes>           [default: [object Object]] Number of minutes to wait for the scratch org to be ready.
+  -y, --duration-days=<days>     [default: [object Object]] Number of days before the org expires.
+  --api-version=<value>          Override the api version used for api requests made by this command
+  --async                        Request the org, but don't wait for it to complete.
+
+PACKAGING FLAGS
+  -c, --no-ancestors  Don't include second-generation managed package (2GP) ancestors in the scratch org.
+  -m, --no-namespace  Create the scratch org with no namespace, even if the Dev Hub has a namespace.
+
+DEFINITION FILE OVERRIDE FLAGS
+  -e, --edition=<option>  Salesforce edition of the scratch org. Overrides the value of the "edition" option in the
+                          definition file, if set.
+                          <options: developer|enterprise|group|professional|partner-developer|partner-enterprise|partner
+                          -group|partner-professional>
+  --admin-email=<value>   Email address that will be applied to the org's admin user. Overrides the value of the
+                          "adminEmail" option in the definition file, if set.
+  --description=<value>   Description of the scratch org in the Dev Hub. Overrides the value of the "description" option
+                          in the definition file, if set.
+  --name=<value>          Name of the org, such as "Acme Company". Overrides the value of the "orgName" option in the
+                          definition file, if set.
+  --release=<option>      Release of the scratch org as compared to the Dev Hub release.
+                          <options: preview|previous>
+  --source-org=<value>    15-character ID of the org whose shape the new scratch org will be based on. Overrides the
+                          value of the "sourceOrg" option in the definition file, if set.
+  --username=<value>      Username of the scratch org admin user. Overrides the value of the "username" option in the
+                          definition file, if set.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Create a scratch org.
+
+  There are two ways to create a scratch org: either specify a definition file that contains the options or use the
+  --edition flag to specify the one required option.
+
+  For either method, you can also use these flags; if you use them with --definition-file, they override their
+  equivalent option in the scratch org definition file:
+
+  * --description
+  * --name  (equivalent to the "orgName" option)
+  * --username
+  * --release
+  * --edition
+  * --admin-email (equivalent to the "adminEmail" option)
+  * --source-org (equivalent to the "sourceOrg" option)
+
+  If you want to set options other than the preceding ones, such as org features or settings, you must use a definition
+  file.
+
+  You must specify a Dev Hub to create a scratch org, either with the --target-dev-hub flag or by setting your default
+  Dev Hub with the target-dev-hub configuration variable.
+
+ALIASES
+  $ sf env create scratch
+
+EXAMPLES
+  Create a Developer edition scratch org using your default Dev Hub and give the scratch org an alias:
+
+    $ sf org create scratch --edition developer --alias my-scratch-org
+
+  Create a scratch org with a definition file. Specify the Dev Hub using its alias, set the scratch org as your
+  default, and specify that it expires in 3 days:
+
+    $ sf org create scratch --target-dev-hub MyHub --definition-file config/project-scratch-def.json --set-default \
+      --duration-days 3
+
+  Create a preview Enterprise edition scratch org; for use only during Salesforce release transition periods:
+
+    $ sf org create scratch --edition enterprise --alias my-scratch-org --target-dev-hub MyHub --release preview
+
+FLAG DESCRIPTIONS
+  -a, --alias=<value>  Alias for the scratch org.
+
+    New scratch orgs include one administrator by default. The admin user's username is auto-generated and looks
+    something like test-wvkpnfm5z113@example.com. When you set an alias for a new scratch org, it's assigned this
+    username.
+
+  -e, --edition=developer|enterprise|group|professional|partner-developer|partner-enterprise|partner-group|partner-professional
+
+    Salesforce edition of the scratch org. Overrides the value of the "edition" option in the definition file, if set.
+
+    The editions that begin with "partner-" are available only if the Dev Hub org is a Partner Business Org.
+
+  -f, --definition-file=<value>  Path to a scratch org definition file.
+
+    The scratch org definition file is a blueprint for the scratch org. It mimics the shape of an org that you use in
+    the development life cycle, such as acceptance testing, packaging, or production. See
+    <https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm> for
+    all the option you can specify in the definition file.
+
+  -t, --[no-]track-source  Use source tracking for this scratch org. Set --no-track-source to disable source tracking.
+
+    We recommend you enable source tracking in scratch orgs, which is why it's the default behavior. Source tracking
+    allows you to track the changes you make to your metadata, both in your local project and in the scratch org, and to
+    detect any conflicts between the two.
+
+    To disable source tracking in the new scratch org, specify the --no-track-source flag. The main reason to disable
+    source tracking is for performance. For example, while you probably want to deploy metadata and run Apex tests in
+    your CI/CD jobs, you probably don't want to incur the costs of source tracking (checking for conflicts, polling the
+    SourceMember object, various file system operations.) This is a good use case for disabling source tracking in the
+    scratch org.
+
+  -v, --target-dev-hub=<value>  Username or alias of the Dev Hub org.
+
+    Overrides the value of the target-dev-hub configuration variable, if set.
+
+  -w, --wait=<minutes>  Number of minutes to wait for the scratch org to be ready.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays
+    the job ID. To resume the scratch org creation, run the org resume scratch command and pass it the job ID.
+
+  --async  Request the org, but don't wait for it to complete.
+
+    The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue
+    to use the CLI. To resume the scratch org creation, run "sf org resume scratch".
+
+  --release=preview|previous  Release of the scratch org as compared to the Dev Hub release.
+
+    By default, scratch orgs are on the same release as the Dev Hub. During Salesforce release transition periods, you
+    can override this default behavior and opt in or out of the new release.
+
+  --username=<value>
+
+    Username of the scratch org admin user. Overrides the value of the "username" option in the definition file, if set.
+
+    The username must be unique within the entire scratch org and sandbox universe. You must add your own logic to
+    ensure uniqueness.
+
+    Omit this flag to have Salesforce generate a unique username for your org.
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/create/scratch.ts)_
+
+## `sf org create user`
+
+Create a user for a scratch org.
+
+```
+USAGE
+  $ sf org create user -o <value> [--json] [-a <value>] [-f <value>] [-s] [--api-version <value>]
+
+FLAGS
+  -a, --set-alias=<value>        Set an alias for the created username to reference in other CLI commands.
+  -f, --definition-file=<value>  File path to a user definition file for customizing the new user.
+  -o, --target-org=<value>       (required) Username or alias of the target org.
+  -s, --set-unique-username      Force the username, if specified in the definition file or at the command line, to be
+                                 unique by appending the org ID.
+  --api-version=<value>          Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Create a user for a scratch org.
+
+  A scratch org includes one administrator user by default. For testing purposes, however, you sometimes need to create
+  additional users.
+
+  The easiest way to create a user is to let this command assign default or generated characteristics to the new user.
+  If you want to customize your new user, create a definition file and specify it with the --definition-file flag. In
+  the file, you can include all the User sObject (SSalesforce object) fields and Salesforce DX-specific options, as
+  described in "User Definition File for Customizing a Scratch Org User"
+  (https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_users_def_file.htm).
+  You can also specify these options on the command line.
+
+  If you don't customize your new user, this command creates a user with the following default characteristics:
+
+  * The username is the existing administrator’s username prepended with a timestamp, such as
+  1505759162830_test-wvkpnfm5z113@example.com.
+  * The user’s profile is Standard User.
+  * The values of the required fields of the User sObject are the corresponding values of the administrator user.
+  * The user has no password.
+
+  Use the --set-alias flag to assign a simple name to the user that you can reference in later CLI commands. This alias
+  is local and different from the Alias field of the User sObject record of the new user, which you set in the Setup UI.
+
+  When this command completes, it displays the new username and user ID. Run the "org display user" command to get more
+  information about the new user.
+
+  For more information about user limits, defaults, and other considerations when creating a new scratch org user, see
+  https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_users.htm.
+
+ALIASES
+  $ sf force user create
+
+EXAMPLES
+  Create a user for your default scratch org and let this command generate a username, user ID, and other
+  characteristics:
+
+    $ sf org create user
+
+  Create a user with alias "testuser1" using a user definition file. Set the "profileName" option to "Chatter Free
+  User", which overrides the value in the defintion file if it also exists there. Create the user for the scratch org
+  with alias "my-scratch":
+
+    $ sf org create user --set-alias testuser1 --definition-file config/project-user-def.json profileName='Chatter \
+      Free User' --target-org my-scratch
+
+  Create a user by specifying the username, email, and perm set assignment at the command line; command fails if the
+  username already exists in Salesforce:
+
+    $ sf org create user username=testuser1@my.org email=me@my.org permsets=DreamHouse
+
+  Create a user with a definition file, set the email value as specified (overriding any value in the definition
+  file), and generate a password for the user. If the username in the definition file isn't unique, the command
+  appends the org ID to make it unique:
+
+    $ sf org create user --definition-file config/project-user-def.json email=me@my.org generatepassword=true \
+      --set-unique-username
+
+FLAG DESCRIPTIONS
+  -f, --definition-file=<value>  File path to a user definition file for customizing the new user.
+
+    The user definition file uses JSON format and can include any Salesforce User sObject field and Salesforce
+    DX-specific options. See
+    https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_users_def_file.htm
+    for more information.
+
+  -s, --set-unique-username
+
+    Force the username, if specified in the definition file or at the command line, to be unique by appending the org
+    ID.
+
+    The new user’s username must be unique across all Salesforce orgs and in the form of an email address. If you let
+    this command generate a username for you, it's guaranteed to be unique. If you specify an existing username in a
+    definition file, the command fails. Set this flag to force the username to be unique; as a result, the username
+    might be different than what you specify in the definition file.
+```
+
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/org/create/user.ts)_
+
+## `sf org delete sandbox`
+
+Delete a sandbox.
+
+```
+USAGE
+  $ sf org delete sandbox -o <value> [--json] [-p]
+
+FLAGS
+  -o, --target-org=<value>  (required) Sandbox alias or login user.
+  -p, --no-prompt           Don't prompt the user to confirm the deletion.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Delete a sandbox.
+
+  Salesforce CLI marks the org for deletion in the production org that contains the sandbox licenses and then deletes
+  all local references to the org from your computer.
+  Specify a sandbox with either the username you used when you logged into it, or the alias you gave the sandbox when
+  you created it. Run "sf org list" to view all your orgs, including sandboxes, and their aliases.
+
+ALIASES
+  $ sf env delete sandbox
+
+EXAMPLES
+  Delete a sandbox with alias my-sandbox:
+
+    $ sf org delete sandbox --target-org my-sandbox
+
+  Specify a username instead of an alias:
+
+    $ sf org delete sandbox --target-org myusername@example.com.qa
+
+  Delete the sandbox without prompting to confirm :
+
+    $ sf org delete sandbox --target-org my-sandbox --no-prompt
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/delete/sandbox.ts)_
+
+## `sf org delete scratch`
+
+Delete a scratch org.
+
+```
+USAGE
+  $ sf org delete scratch -o <value> [--json] [-p]
+
+FLAGS
+  -o, --target-org=<value>  (required) Scratch org alias or login user.
+  -p, --no-prompt           Don't prompt the user to confirm the deletion.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Delete a scratch org.
+
+  Salesforce CLI marks the org for deletion in the Dev Hub org and then deletes all local references to the org from
+  your computer.
+  Specify a scratch org with either the username or the alias you gave the scratch org when you created it. Run "sf org
+  list" to view all your orgs, including scratch orgs, and their aliases.
+
+ALIASES
+  $ sf env delete scratch
+
+EXAMPLES
+  Delete a scratch org with alias my-scratch-org:
+
+    $ sf org delete scratch --target-org my-scratch-org
+
+  Specify a username instead of an alias:
+
+    $ sf org delete scratch --target-org test-123456-abcdefg@example.com
+
+  Delete the scratch org without prompting to confirm :
+
+    $ sf org delete scratch --target-org my-scratch-org --no-prompt
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/delete/scratch.ts)_
+
+## `sf org display`
+
+Display information about an org.
+
+```
+USAGE
+  $ sf org display -o <value> [--json] [--api-version <value>] [--verbose]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --verbose                 Display the sfdxAuthUrl property.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Display information about an org.
+
+  Output includes your access token, client Id, connected status, org ID, instance URL, username, and alias, if
+  applicable.
+
+  Use --verbose to include the SFDX auth URL. WARNING: The SFDX auth URL contains sensitive information, such as a
+  refresh token that can be used to access an org. Don't share or distribute this URL or token.
+
+  Including --verbose displays the sfdxAuthUrl property only if you authenticated to the org using "org login web" (not
+  "org login jwt").
+
+ALIASES
+  $ sf force org display
+
+EXAMPLES
+  Display information about your default org:
+
+    $ sf org display
+
+  Display information, including the sfdxAuthUrl property, about the org with alias TestOrg1:
+
+    $ sf org display --target-org TestOrg1 --verbose
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/display.ts)_
+
+## `sf org display user`
+
+Display information about a Salesforce user.
+
+```
+USAGE
+  $ sf org display user -o <value> [--json] [--api-version <value>]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Display information about a Salesforce user.
+
+  Output includes the profile name, org ID, access token, instance URL, login URL, and alias if applicable. The
+  displayed alias is local and different from the Alias field of the User sObject record of the new user, which you set
+  in the Setup UI.
+
+ALIASES
+  $ sf force user display
+
+EXAMPLES
+  Display information about the admin user of your default scratch org:
+
+    $ sf org display user
+
+  Display information about the specified user and output in JSON format:
+
+    $ sf org display user --target-org me@my.org --json
+```
+
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/org/display/user.ts)_
+
+## `sf org generate password`
+
+Generate a random password for scratch org users.
+
+```
+USAGE
+  $ sf org generate password -o <value> [--json] [-b <value>] [-l <value>] [-c <value>] [--api-version <value>]
+
+FLAGS
+  -b, --on-behalf-of=<value>...  Comma-separated list of usernames or aliases to assign the password to.
+  -c, --complexity=<value>       [default: 5] Level of password complexity or strength; the higher the value, the
+                                 stronger the password.
+  -l, --length=<value>           [default: 13] Number of characters in the generated password; valid values are between
+                                 8 and 100.
+  -o, --target-org=<value>       (required) Username or alias of the target org.
+  --api-version=<value>          Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Generate a random password for scratch org users.
+
+  By default, new scratch orgs contain one admin user with no password. Use this command to generate or change a
+  password for any scratch org user. After it's set, you can’t unset a password, you can only change it.
+
+  To change the password strength, set the --complexity flag to a value between 0 and 5. Each value specifies the types
+  of characters used in the generated password:
+
+  0 - lower case letters only
+  1 - lower case letters and numbers only
+  2 - lower case letters and symbols only
+  3 - lower and upper case letters and numbers only
+  4 - lower and upper case letters and symbols only
+  5 - lower and upper case letters and numbers and symbols only
+
+  To see a password that was previously generated, run "org display user".
+
+EXAMPLES
+  Generate a password for the original admin user of your default scratch org:
+
+    $ sf org generate password
+
+  Generate a password that contains 12 characters for the original admin user of the scratch org with alias
+  "my-scratch":
+
+    $ sf org generate password --length 12 --target-org my-scratch
+
+  Generate a password for your default scratch org admin user that uses lower and upper case letters and numbers only:
+
+    $ sf org generate password --complexity 3
+
+  Generate a password for the specified users in the default scratch org:
+
+    $ sf org generate password --on-behalf-of user1@my.org --on-behalf-of user2@my.org --on-behalf-of user3@my.org
+```
+
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/org/generate/password.ts)_
+
+## `sf org list`
+
+List all orgs you’ve created or authenticated to.
+
+```
+USAGE
+  $ sf org list [--json] [--verbose] [--all] [-p --clean] [--skip-connection-status]
+
+FLAGS
+  -p, --no-prompt           Don't prompt for confirmation.
+  --all                     Include expired, deleted, and unknown-status scratch orgs.
+  --clean                   Remove all local org authorizations for non-active scratch orgs. Use "org logout" to remove
+                            non-scratch orgs.
+  --skip-connection-status  Skip retrieving the connection status of non-scratch orgs.
+  --verbose                 List more information about each org.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+ALIASES
+  $ sf force org list
+
+EXAMPLES
+  List all orgs you've created or authenticated to:
+
+    $ sf org list
+
+  List all orgs, including expired, deleted, and unknown-status orgs; don't include the connection status:
+
+    $ sf org list --skip-connection-status --all
+
+  List orgs and remove local org authorization info about non-active scratch orgs:
+
+    $ sf org list --clean
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/list.ts)_
+
+## `sf org list auth`
+
+List authorization information about the orgs you created or logged into.
+
+```
+USAGE
+  $ sf org list auth [--json]
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List authorization information about the orgs you created or logged into.
+
+  This command uses local authorization information that Salesforce CLI caches when you create a scratch org or log into
+  an org. The command doesn't actually connect to the orgs to verify that they're still active. As a result, this
+  command executes very quickly. If you want to view live information about your authorized orgs, such as their
+  connection status, use the "org list" command.
+
+ALIASES
+  $ sf force auth list
+  $ sf auth list
+
+EXAMPLES
+  List local authorization information about your orgs:
+
+    $ sf org list auth
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/list/auth.ts)_
+
+## `sf org list metadata`
+
+List the metadata components and properties of a specified type.
+
+```
+USAGE
+  $ sf org list metadata -o <value> -m <value> [--json] [--api-version <value>] [-f <value>] [--folder <value>]
+
+FLAGS
+  -f, --output-file=<value>    Pathname of the file in which to write the results.
+  -m, --metadata-type=<value>  (required) Metadata type to be retrieved, such as CustomObject; metadata type names are
+                               case-sensitive.
+  -o, --target-org=<value>     (required) Username or alias of the target org.
+  --api-version=<value>        API version to use; default is the most recent API version.
+  --folder=<value>             Folder associated with the component; required for components that use folders; folder
+                               names are case-sensitive.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List the metadata components and properties of a specified type.
+
+  Use this command to identify individual components in your manifest file or if you want a high-level view of
+  particular metadata types in your org. For example, you can use this command to return a list of names of all the
+  CustomObject or Layout components in your org, then use this information in a retrieve command that returns a subset
+  of these components.
+
+  The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API
+  Functions permission.
+
+ALIASES
+  $ sf force mdapi listmetadata
+
+EXAMPLES
+  List the CustomObject components, and their properties, in the org with alias "my-dev-org":
+
+    $ sf org list metadata --metadata-type CustomObject --target-org my-dev-org
+
+  List the CustomObject components in your default org, write the output to the specified file, and use API version
+  57.0:
+
+    $ sf org list metadata --metadata-type CustomObject --api-version 57.0 --output-file /path/to/outputfilename.txt
+
+  List the Dashboard components in your default org that are contained in the "folderSales" folder, write the output
+  to the specified file, and use API version 57.0:
+
+    $ sf org list metadata --metadata-type Dashboard --folder folderSales --api-version 57.0 --output-file \
+      /path/to/outputfilename.txt
+
+FLAG DESCRIPTIONS
+  --api-version=<value>  API version to use; default is the most recent API version.
+
+    Override the api version used for api requests made by this command
+
+  --folder=<value>
+
+    Folder associated with the component; required for components that use folders; folder names are case-sensitive.
+
+    Examples of metadata types that use folders are Dashboard, Document, EmailTemplate, and Report.
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/list/metadata.ts)_
+
+## `sf org list metadata-types`
+
+Display details about the metadata types that are enabled for your org.
+
+```
+USAGE
+  $ sf org list metadata-types -o <value> [--json] [--api-version <value>] [-f <value>]
+
+FLAGS
+  -f, --output-file=<value>  Pathname of the file in which to write the results.
+  -o, --target-org=<value>   (required) Username or alias of the target org.
+  --api-version=<value>      API version to use; default is the most recent API version.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Display details about the metadata types that are enabled for your org.
+
+  The information includes Apex classes and triggers, custom objects, custom fields on standard objects, tab sets that
+  define an app, and many other metadata types. Use this information to identify the syntax needed for a <name> element
+  in a manifest file (package.xml).
+
+  The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API
+  Functions permission.
+
+ALIASES
+  $ sf force mdapi describemetadata
+
+EXAMPLES
+  Display information about all known and enabled metadata types in the org with alias "my-dev-org" using API version
+  57.0:
+
+    $ sf org list metadata-types --api-version 57.0 --target-org my-dev-org
+
+  Display only the metadata types that aren't yet supported by Salesforce CLI in your default org and write the
+  results to the specified file:
+
+    $ sf org list metadata-types --output-file /path/to/outputfilename.txt --filter-known
+
+FLAG DESCRIPTIONS
+  -f, --output-file=<value>  Pathname of the file in which to write the results.
+
+    Directing the output to a file makes it easier to extract relevant information for your package.xml manifest file.
+    The default output destination is the terminal or command window console.
+
+  --api-version=<value>  API version to use; default is the most recent API version.
+
+    Override the api version used for api requests made by this command
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/list/metadata-types.ts)_
+
+## `sf org list users`
+
+List all locally-authenticated users of an org.
+
+```
+USAGE
+  $ sf org list users -o <value> [--json] [--api-version <value>]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List all locally-authenticated users of an org.
+
+  For scratch orgs, the list includes any users you've created with the "org create user" command; the original scratch
+  org admin user is marked with "(A)". For other orgs, the list includes the users you used to authenticate to the org.
+
+ALIASES
+  $ sf force user list
+
+EXAMPLES
+  List the locally-authenticated users of your default org:
+
+    $ sf org list users
+
+  List the locally-authenticated users of the specified org:
+
+    $ sf org list users --target-org me@my.org
+```
+
+_See code: [@salesforce/plugin-user](https://github.com/salesforcecli/plugin-user/blob/2.3.33/src/commands/org/list/users.ts)_
+
+## `sf org login access-token`
+
+Authorize an org using an existing Salesforce access token.
+
+```
+USAGE
+  $ sf org login access-token -r <value> [--json] [-d] [-s] [-a <value>] [-p]
+
+FLAGS
+  -a, --alias=<value>         Alias for the org.
+  -d, --set-default-dev-hub   Set the authenticated org as the default Dev Hub.
+  -p, --no-prompt             Don't prompt for confirmation.
+  -r, --instance-url=<value>  (required) URL of the instance that the org lives on.
+  -s, --set-default           Set the authenticated org as the default that all org-related commands run against.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Authorize an org using an existing Salesforce access token.
+
+  By default, the command runs interactively and asks you for the access token. If you previously authorized the org,
+  the command prompts whether you want to overwrite the local file. Specify --no-prompt to not be prompted.
+
+  To use the command in a CI/CD script, set the SFDX_ACCESS_TOKEN environment variable to the access token. Then run the
+  command with the --no-prompt parameter.
+
+ALIASES
+  $ sf force auth accesstoken store
+  $ sf auth accesstoken store
+
+EXAMPLES
+  Authorize an org on https://mycompany.my.salesforce.com; the command prompts you for the access token:
+
+    $ sf org login access-token --instance-url https://mycompany.my.salesforce.com
+
+  Authorize the org without being prompted; you must have previously set the SFDX_ACCESS_TOKEN environment variable to
+  the access token:
+
+    $ sf org login access-token --instance-url https://dev-hub.my.salesforce.com --no-prompt
+
+FLAG DESCRIPTIONS
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+
+    If you specify an --instance-url value, this value overrides the sfdcLoginUrl value in your sfdx-project.json file.
+
+    To specify a My Domain URL, use the format https://yourcompanyname.my.salesforce.com.
+
+    To specify a sandbox, set --instance-url to https://MyDomainName--SandboxName.sandbox.my.salesforce.com.
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/login/access-token.ts)_
+
+## `sf org login device`
+
+Authorize an org using a device code.
+
+```
+USAGE
+  $ sf org login device [--json] [-i <value>] [-r <value>] [-d] [-s] [-a <value>]
+
+FLAGS
+  -a, --alias=<value>         Alias for the org.
+  -d, --set-default-dev-hub   Set the authenticated org as the default Dev Hub.
+  -i, --client-id=<value>     OAuth client ID (also called consumer key) of your custom connected app.
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+  -s, --set-default           Set the authenticated org as the default that all org-related commands run against.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Authorize an org using a device code.
+
+  Use this command to allow a device to connect to an org.
+
+  When you run this command, it first displays an 8-digit device code and the URL for verifying the code on your org.
+  The default instance URL is https://login.salesforce.com, so if the org you're authorizing is on a different instance,
+  use the --instance-url. The command waits while you complete the verification. Open a browser and navigate to the
+  displayed verification URL, enter the code, then click Connect. If you aren't already logged into your org, log in,
+  and then you're prompted to allow the device to connect to the org. After you successfully authorize the org, you can
+  close the browser window.
+
+ALIASES
+  $ sf force auth device login
+  $ sf auth device login
+
+EXAMPLES
+  Authorize an org using a device code, give the org the alias TestOrg1, and set it as your default Dev Hub org:
+
+    $ sf org login device --set-default-dev-hub --alias TestOrg1
+
+  Authorize an org in which you've created a custom connected app with the specified client ID (consumer key):
+
+    $ sf org login device --client-id <OAuth client id>
+
+  Authorize a sandbox org with the specified instance URL:
+
+    $ sf org login device --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com
+
+FLAG DESCRIPTIONS
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+
+    If you specify an --instance-url value, this value overrides the sfdcLoginUrl value in your sfdx-project.json file.
+
+    To specify a My Domain URL, use the format https://yourcompanyname.my.salesforce.com.
+
+    To specify a sandbox, set --instance-url to https://MyDomainName--SandboxName.sandbox.my.salesforce.com.
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/login/device.ts)_
+
+## `sf org login jwt`
+
+Log in to a Salesforce org using a JSON web token (JWT).
+
+```
+USAGE
+  $ sf org login jwt -o <value> -f <value> -i <value> [--json] [-r <value>] [-d] [-s] [-a <value>]
+
+FLAGS
+  -a, --alias=<value>         Alias for the org.
+  -d, --set-default-dev-hub   Set the authenticated org as the default Dev Hub.
+  -f, --jwt-key-file=<value>  (required) Path to a file containing the private key.
+  -i, --client-id=<value>     (required) OAuth client ID (also called consumer key) of your custom connected app.
+  -o, --username=<value>      (required) Username of the user logging in.
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+  -s, --set-default           Set the authenticated org as the default that all org-related commands run against.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Log in to a Salesforce org using a JSON web token (JWT).
+
+  Use this command in automated environments where you can’t interactively log in with a browser, such as in CI/CD
+  scripts.
+
+  Logging into an org authorizes the CLI to run other commands that connect to that org, such as deploying or retrieving
+  a project. You can log into many types of orgs, such as sandboxes, Dev Hubs, Env Hubs, production orgs, and scratch
+  orgs.
+
+  Complete these steps before you run this command:
+
+  1. Create a digital certificate (also called digital signature) and the private key to sign the certificate. You can
+  use your own key and certificate issued by a certification authority. Or use OpenSSL to create a key and a self-signed
+  digital certificate.
+  2. Store the private key in a file on your computer. When you run this command, you set the --jwt-key-file flag to
+  this file.
+  3. Create a custom connected app in your org using the digital certificate. Make note of the consumer key (also called
+  client id) that’s generated for you. Be sure the username of the user logging in is approved to use the connected app.
+  When you run this command, you set the --client-id flag to the consumer key.
+
+  See https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_jwt_flow.htm for more
+  information.
+
+  We recommend that you set an alias when you log into an org. Aliases make it easy to later reference this org when
+  running commands that require it. If you don’t set an alias, you use the username that you specified when you logged
+  in to the org. If you run multiple commands that reference the same org, consider setting the org as your default. Use
+  --set-default for your default scratch org or sandbox, or --set-default-dev-hub for your default Dev Hub.
+
+ALIASES
+  $ sf force auth jwt grant
+  $ sf auth jwt grant
+
+EXAMPLES
+  Log into an org with username jdoe@example.org and on the default instance URL (https://login.salesforce.org). The
+  private key is stored in the file /Users/jdoe/JWT/server.key and the command uses the connected app with consumer
+  key (client id) 04580y4051234051.
+
+    $ sf org login jwt --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id \
+      04580y4051234051
+
+  Set the org as the default and give it an alias:
+
+    $ sf org login jwt --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id \
+      04580y4051234051 --alias ci-org --set-default
+
+  Set the org as the default Dev Hub and give it an alias:
+
+    $ sf org login jwt --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id \
+      04580y4051234051 --alias ci-dev-hub --set-default-dev-hub
+
+  Log in to a sandbox using URL https://MyDomainName--SandboxName.sandbox.my.salesforce.com:
+
+    $ sf org login jwt --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id \
+      04580y4051234051 --alias ci-org --set-default --instance-url \
+      https://MyDomainName--SandboxName.sandbox.my.salesforce.com
+
+FLAG DESCRIPTIONS
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+
+    If you specify an --instance-url value, this value overrides the sfdcLoginUrl value in your sfdx-project.json file.
+
+    To specify a My Domain URL, use the format https://yourcompanyname.my.salesforce.com.
+
+    To specify a sandbox, set --instance-url to https://MyDomainName--SandboxName.sandbox.my.salesforce.com.
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/login/jwt.ts)_
+
+## `sf org login sfdx-url`
+
+Authorize an org using a Salesforce DX authorization URL stored in a file.
+
+```
+USAGE
+  $ sf org login sfdx-url -f <value> [--json] [-d] [-s] [-a <value>]
+
+FLAGS
+  -a, --alias=<value>          Alias for the org.
+  -d, --set-default-dev-hub    Set the authenticated org as the default Dev Hub.
+  -f, --sfdx-url-file=<value>  (required) Path to a file that contains the Salesforce DX authorization URL.
+  -s, --set-default            Set the authenticated org as the default that all org-related commands run against.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Authorize an org using a Salesforce DX authorization URL stored in a file.
+
+  The Salesforce DX (SFDX) authorization URL must have the format
+  "force://<clientId>:<clientSecret>:<refreshToken>@<instanceUrl>". NOTE: The SFDX authorization URL uses the "force"
+  protocol, and not "http" or "https". Also, the "instanceUrl" inside the SFDX authorization URL doesn't include the
+  protocol ("https://").
+
+  You have three options when creating the authorization file. The easiest option is to redirect the output of the "sf
+  org display --verbose --json" command into a file. For example, using an org with alias my-org that you've already
+  authorized:
+
+  $ sf org display --target-org my-org --verbose --json > authFile.json
+
+  The resulting JSON file contains the URL in the "sfdxAuthUrl" property of the "result" object. You can then reference
+  the file when running this command:
+
+  $ sf org login sfdx-url --sfdx-url-file authFile.json
+
+  NOTE: The "sf org display --verbose" command displays the refresh token only for orgs authorized with the web server
+  flow, and not the JWT bearer flow.
+
+  You can also create a JSON file that has a top-level property named sfdxAuthUrl whose value is the authorization URL.
+  Finally, you can create a normal text file that includes just the URL and nothing else.
+
+ALIASES
+  $ sf force auth sfdxurl store
+  $ sf auth sfdxurl store
+
+EXAMPLES
+  Authorize an org using the SFDX authorization URL in the files/authFile.json file:
+
+    $ sf org login sfdx-url --sfdx-url-file files/authFile.json
+
+  Similar to previous example, but set the org as your default and give it an alias MyDefaultOrg:
+
+    $ sf org login sfdx-url --sfdx-url-file files/authFile.json --set-default --alias MyDefaultOrg
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/login/sfdx-url.ts)_
+
+## `sf org login web`
+
+Log in to a Salesforce org using the web server flow.
+
+```
+USAGE
+  $ sf org login web [--json] [-b chrome|edge|firefox] [-i <value>] [-r <value>] [-d] [-s] [-a <value>]
+
+FLAGS
+  -a, --alias=<value>         Alias for the org.
+  -b, --browser=<option>      Browser in which to open the org.
+                              <options: chrome|edge|firefox>
+  -d, --set-default-dev-hub   Set the authenticated org as the default Dev Hub.
+  -i, --client-id=<value>     OAuth client ID (also called consumer key) of your custom connected app.
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+  -s, --set-default           Set the authenticated org as the default that all org-related commands run against.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Log in to a Salesforce org using the web server flow.
+
+  Opens a Salesforce instance URL in a web browser so you can enter your credentials and log in to your org. After you
+  log in, you can close the browser window.
+
+  Logging into an org authorizes the CLI to run other commands that connect to that org, such as deploying or retrieving
+  metadata. You can log into many types of orgs, such as sandboxes, Dev Hubs, Env Hubs, production orgs, and scratch
+  orgs.
+
+  We recommend that you set an alias when you log into an org. Aliases make it easy to later reference this org when
+  running commands that require it. If you don’t set an alias, you use the username that you specified when you logged
+  in to the org. If you run multiple commands that reference the same org, consider setting the org as your default. Use
+  --set-default for your default scratch org or sandbox, or --set-default-dev-hub for your default Dev Hub.
+
+  By default, this command uses the global out-of-the-box connected app in your org. If you need more security or
+  control, such as setting the refresh token timeout or specifying IP ranges, create your own connected app using a
+  digital certificate. Make note of the consumer key (also called cliend id) that’s generated for you. Then specify the
+  consumer key with the --client-id flag.
+
+ALIASES
+  $ sf force auth web login
+  $ sf auth web login
+
+EXAMPLES
+  Run the command with no flags to open the default Salesforce login page (https://login.salesforce.com):
+
+    $ sf org login web
+
+  Log in to your Dev Hub, set it as your default Dev Hub, and set an alias that you reference later when you create a
+  scratch org:
+
+    $ sf org login web --set-default-dev-hub --alias dev-hub
+
+  Log in to a sandbox and set it as your default org:
+
+    $ sf org login web --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com --set-default
+
+  Use --browser to specify a specific browser, such as Google Chrome:
+
+    $ sf org login web --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com --set-default \
+      --browser chrome
+
+  Use your own connected app by specifying its consumer key (also called client ID):
+
+    $ sf org login web --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com --set-default \
+      --browser chrome --client-id 04580y4051234051
+
+FLAG DESCRIPTIONS
+  -b, --browser=chrome|edge|firefox  Browser in which to open the org.
+
+    If you don’t specify --browser, the command uses your default browser. The exact names of the browser applications
+    differ depending on the operating system you're on; check your documentation for details.
+
+  -r, --instance-url=<value>  URL of the instance that the org lives on.
+
+    If you specify an --instance-url value, this value overrides the sfdcLoginUrl value in your sfdx-project.json file.
+
+    To specify a My Domain URL, use the format https://yourcompanyname.my.salesforce.com.
+
+    To specify a sandbox, set --instance-url to https://MyDomainName--SandboxName.sandbox.my.salesforce.com.
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/login/web.ts)_
+
+## `sf org logout`
+
+Log out of a Salesforce org.
+
+```
+USAGE
+  $ sf org logout [--json] [-a | -o <value>] [-p]
+
+FLAGS
+  -a, --all                 Include all authenticated orgs.
+  -o, --target-org=<value>  Username or alias of the target org.
+  -p, --no-prompt           Don't prompt for confirmation.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Log out of a Salesforce org.
+
+  If you run this command with no flags and no default org set in your config or environment, it first displays a list
+  of orgs you've created or logged into, with none of the orgs selected. Use the arrow keys to scroll through the list
+  and the space bar to select the orgs you want to log out of. Press Enter when you're done; the command asks for a
+  final confirmation before logging out of the selected orgs.
+
+  The process is similar if you specify --all, except that in the initial list of orgs, they're all selected. Use
+  --target-org to logout of a specific org. In both these cases by default, you must still confirm that you want to log
+  out. Use --no-prompt to never be asked for confirmation when also using --all or --target-org.
+
+  Be careful! If you log out of a scratch org without having access to its password, you can't access the scratch org
+  again, either through the CLI or the Salesforce UI.
+
+ALIASES
+  $ sf force auth logout
+  $ sf auth logout
+
+EXAMPLES
+  Interactively select the orgs to log out of:
+
+    $ sf org logout
+
+  Log out of the org with username me@my.org:
+
+    $ sf org logout --target-org me@my.org
+
+  Log out of all orgs after confirmation:
+
+    $ sf org logout --all
+
+  Logout of the org with alias my-scratch and don't prompt for confirmation:
+
+    $ sf org logout --target-org my-scratch --no-prompt
+
+FLAG DESCRIPTIONS
+  -a, --all  Include all authenticated orgs.
+
+    All orgs includes Dev Hubs, sandboxes, DE orgs, and expired, deleted, and unknown-status scratch orgs.
+```
+
+_See code: [@salesforce/plugin-auth](https://github.com/salesforcecli/plugin-auth/blob/2.8.18/src/commands/org/logout.ts)_
+
+## `sf org open`
+
+Open your default scratch org, or another specified org, in a browser.
+
+```
+USAGE
+  $ sf org open -o <value> [--json] [--api-version <value>] [-b chrome|edge|firefox | -r] [-p <value> | -f
+    <value>]
+
+FLAGS
+  -b, --browser=<option>     Browser where the org opens.
+                             <options: chrome|edge|firefox>
+  -f, --source-file=<value>  Path to an ApexPage or FlexiPage to open in Lightning App Builder.
+  -o, --target-org=<value>   (required) Username or alias of the target org.
+  -p, --path=<value>         Navigation URL path to open a specific page.
+  -r, --url-only             Display navigation URL, but don’t launch browser.
+  --api-version=<value>      Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Open your default scratch org, or another specified org, in a browser.
+
+  To open a specific page, specify the portion of the URL after "https://MyDomainName.my.salesforce.com/" as the value
+  for the --path flag. For example, specify "--path lightning" to open Lightning Experience, or specify "--path
+  /apex/YourPage" to open a Visualforce page.
+
+  Use the --source-file to open a Lightning Page from your local project in Lightning App Builder. Lightning page files
+  have the suffix .flexipage-meta.xml, and are stored in the "flexipages" directory.
+
+  To generate a URL but not launch it in your browser, specify --url-only.
+
+  To open in a specific browser, use the --browser flag. Supported browsers are "chrome", "edge", and "firefox". If you
+  don't specify --browser, the org opens in your default browser.
+
+ALIASES
+  $ sf force org open
+  $ sf force source open
+
+EXAMPLES
+  Open your default org in your default browser:
+
+    $ sf org open
+
+  Open the org with alias MyTestOrg1 in the Firefox browser:
+
+    $ sf org open --target-org MyTestOrg1 --browser firefox
+
+  Display the navigation URL for the Lightning Experience page for your default org, but don't open the page in a
+  browser:
+
+    $ sf org open --url-only --path lightning
+
+  Open a local Lightning page in your default org's Lightning App Builder:
+
+    $ sf org open --source-path force-app/main/default/flexipages/Hello.flexipage-meta.xml
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/open.ts)_
+
+## `sf org resume sandbox`
+
+Check the status of a sandbox creation, and log in to it if it's ready.
+
+```
+USAGE
+  $ sf org resume sandbox [--json] [-w <value>] [-n <value> | -i <value>] [-l] [-o <value>]
+
+FLAGS
+  -i, --job-id=<value>      Job ID of the incomplete sandbox creation that you want to check the status of.
+  -l, --use-most-recent     Use the most recent sandbox create request.
+  -n, --name=<value>        Name of the sandbox org.
+  -o, --target-org=<value>  Username or alias of the production org that contains the sandbox license.
+  -w, --wait=<minutes>      Number of minutes to wait for the sandbox org to be ready.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Check the status of a sandbox creation, and log in to it if it's ready.
+
+  Sandbox creation can take a long time. If the original "sf org create sandbox" command either times out, or you
+  specified the --async flag, the command displays a job ID. Use this job ID to check whether the sandbox creation is
+  complete, and if it is, the command then logs into it.
+
+  You can also use the sandbox name to check the status or the --use-most-recent flag to use the job ID of the most
+  recent sandbox creation.
+
+ALIASES
+  $ sf env resume sandbox
+
+EXAMPLES
+  Check the status of a sandbox creation using its name and specify a production org with alias "prodOrg":
+
+    $ sf org resume sandbox --name mysandbox --target-org prodOrg
+
+  Check the status using the job ID:
+
+    $ sf org resume sandbox --job-id 0GRxxxxxxxx
+
+  Check the status of the most recent sandbox create request:
+
+    $ sf org resume sandbox --use-most-recent
+
+FLAG DESCRIPTIONS
+  -i, --job-id=<value>  Job ID of the incomplete sandbox creation that you want to check the status of.
+
+    The job ID is valid for 24 hours after you start the sandbox creation.
+
+  -o, --target-org=<value>  Username or alias of the production org that contains the sandbox license.
+
+    When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to
+    the new sandbox org.
+
+  -w, --wait=<minutes>  Number of minutes to wait for the sandbox org to be ready.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
+    returns the job ID. To resume checking the sandbox creation, rerun this command.
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/resume/sandbox.ts)_
+
+## `sf org resume scratch`
+
+Resume the creation of an incomplete scratch org.
+
+```
+USAGE
+  $ sf org resume scratch [--json] [-i <value>] [-r]
+
+FLAGS
+  -i, --job-id=<value>   Job ID of the incomplete scratch org create that you want to resume.
+  -r, --use-most-recent  Use the job ID of the most recent incomplete scratch org.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Resume the creation of an incomplete scratch org.
+
+  When the original "sf org create scratch" command either times out or is run with the --async flag, it displays a job
+  ID.
+
+  Run this command by either passing it a job ID or using the --use-most-recent flag to specify the most recent
+  incomplete scratch org.
+
+ALIASES
+  $ sf env resume scratch
+
+EXAMPLES
+  Resume a scratch org create with a job ID:
+
+    $ sf org resume scratch --job-id 2SR3u0000008fBDGAY
+
+  Resume your most recent incomplete scratch org:
+
+    $ sf org resume scratch --use-most-recent
+
+FLAG DESCRIPTIONS
+  -i, --job-id=<value>  Job ID of the incomplete scratch org create that you want to resume.
+
+    The job ID is the same as the record ID of the incomplete scratch org in the ScratchOrgInfo object of the Dev Hub.
+
+    The job ID is valid for 24 hours after you start the scratch org creation.
+```
+
+_See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/2.10.9/src/commands/org/resume/scratch.ts)_
+
+## `sf plugins`
+
+List installed plugins.
+
+```
+USAGE
+  $ sf plugins [--json] [--core]
+
+FLAGS
+  --core  Show core plugins.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List installed plugins.
+
+EXAMPLES
+  $ sf plugins
+```
+
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/3.8.3/src/commands/plugins/index.ts)_
+
+## `sf plugins discover`
+
+See a list of 3rd-party sf plugins you can install.
+
+```
+USAGE
+  $ sf plugins discover [--json]
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+EXAMPLES
+  $ sf plugins discover
+```
+
+_See code: [@salesforce/plugin-marketplace](https://github.com/salesforcecli/plugin-template-sf/blob/0.2.3/src/commands/plugins/discover.ts)_
+
+## `sf plugins:inspect PLUGIN...`
+
+Displays installation properties of a plugin.
+
+```
+USAGE
+  $ sf plugins:inspect PLUGIN...
+
+ARGUMENTS
+  PLUGIN  [default: .] Plugin to inspect.
+
+FLAGS
+  -h, --help     Show CLI help.
+  -v, --verbose
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Displays installation properties of a plugin.
+
+EXAMPLES
+  $ sf plugins:inspect myplugin
+```
+
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/3.8.3/src/commands/plugins/inspect.ts)_
+
+## `sf plugins:install PLUGIN...`
+
+Installs a plugin into the CLI.
+
+```
+USAGE
+  $ sf plugins:install PLUGIN...
+
+ARGUMENTS
+  PLUGIN  Plugin to install.
+
+FLAGS
+  -f, --force    Run yarn install with force flag.
+  -h, --help     Show CLI help.
+  -v, --verbose
+
+DESCRIPTION
+  Installs a plugin into the CLI.
+  Can be installed from npm or a git url.
+
+  Installation of a user-installed plugin will override a core plugin.
+
+  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
+  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
+  the CLI without the need to patch and update the whole CLI.
+
+
+ALIASES
+  $ sf plugins add
+
+EXAMPLES
+  $ sf plugins:install myplugin
+
+  $ sf plugins:install https://github.com/someuser/someplugin
+
+  $ sf plugins:install someuser/someplugin
+```
+
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/3.8.3/src/commands/plugins/install.ts)_
+
+## `sf plugins:link PLUGIN`
+
+Links a plugin into the CLI for development.
+
+```
+USAGE
+  $ sf plugins:link PLUGIN
+
+ARGUMENTS
+  PATH  [default: .] path to plugin
+
+FLAGS
+  -h, --help     Show CLI help.
+  -v, --verbose
+
+DESCRIPTION
+  Links a plugin into the CLI for development.
+  Installation of a linked plugin will override a user-installed or core plugin.
+
+  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
+  command will override the user-installed or core plugin implementation. This is useful for development work.
+
+
+EXAMPLES
+  $ sf plugins:link myplugin
+```
+
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/3.8.3/src/commands/plugins/link.ts)_
+
+## `sf plugins trust verify`
+
+Validate a digital signature.
+
+```
+USAGE
+  $ sf plugins trust verify -n <value> [--json] [-r <value>]
+
+FLAGS
+  -n, --npm=<value>       (required) Specify the npm name. This can include a tag/version.
+  -r, --registry=<value>  The registry name. The behavior is the same as npm.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Validate a digital signature.
+
+  Verifies the digital signature on an npm package matches the signature and key stored at the expected URLs.
+
+EXAMPLES
+  $ sf plugins trust verify --npm @scope/npmName --registry http://my.repo.org:4874
+
+  $ sf plugins trust verify --npm @scope/npmName
+```
+
+_See code: [@salesforce/plugin-trust](https://github.com/salesforcecli/plugin-trust/blob/2.6.16/src/commands/plugins/trust/verify.ts)_
+
+## `sf plugins:uninstall PLUGIN...`
+
+Removes a plugin from the CLI.
+
+```
+USAGE
+  $ sf plugins:uninstall PLUGIN...
+
+ARGUMENTS
+  PLUGIN  plugin to uninstall
+
+FLAGS
+  -h, --help     Show CLI help.
+  -v, --verbose
+
+DESCRIPTION
+  Removes a plugin from the CLI.
+
+ALIASES
+  $ sf plugins unlink
+  $ sf plugins remove
+```
+
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/3.8.3/src/commands/plugins/uninstall.ts)_
+
+## `sf plugins update`
+
+Update installed plugins.
+
+```
+USAGE
+  $ sf plugins update [-h] [-v]
+
+FLAGS
+  -h, --help     Show CLI help.
+  -v, --verbose
+
+DESCRIPTION
+  Update installed plugins.
+```
+
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/3.8.3/src/commands/plugins/update.ts)_
+
+## `sf project convert mdapi`
+
+Convert metadata retrieved via Metadata API into the source format used in Salesforce DX projects.
+
+```
+USAGE
+  $ sf project convert mdapi -r <value> [--json] [--api-version <value>] [-d <value>] [-p <value> | -x <value> | -m
+  <value>]
+
+FLAGS
+  -d, --output-dir=<value>       Directory to store your files in after they’re converted to source format; can be an
+                                 absolute or relative path.
+  -m, --metadata=<value>...      Metadata component names to convert.
+  -p, --metadata-dir=<value>...  Root of directory or zip file of metadata formatted files to convert.
+  -r, --root-dir=<value>         (required) Root directory that contains the Metadata API–formatted metadata.
+  -x, --manifest=<value>         File path to manifest (package.xml) of metadata types to convert.
+  --api-version=<value>          Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Convert metadata retrieved via Metadata API into the source format used in Salesforce DX projects.
+
+  To use Salesforce CLI to work with components that you retrieved via Metadata API, first convert your files from the
+  metadata format to the source format using this command.
+
+  To convert files from the source format back to the metadata format, run "sf project convert source".
+
+  To convert multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with
+  multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax
+  applies to --manifest and --source-dir.
+
+ALIASES
+  $ sf force mdapi convert
+
+EXAMPLES
+  Convert metadata formatted files in the specified directory into source formatted files; writes converted files to
+  your default package directory:
+
+    $ sf project convert mdapi --root-dir path/to/metadata
+
+  Similar to previous example, but writes converted files to the specified output directory:
+
+    $ sf project convert mdapi --root-dir path/to/metadata --output-dir path/to/outputdir
+
+FLAG DESCRIPTIONS
+  -p, --metadata-dir=<value>...  Root of directory or zip file of metadata formatted files to convert.
+
+    The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all metadata types in the directory and its sub-directories).
+
+    If you specify this flag, don’t specify --manifest or --metadata. If the comma-separated list you’re supplying
+    contains spaces, enclose the entire comma-separated list in one set of double quotes.
+
+  -x, --manifest=<value>  File path to manifest (package.xml) of metadata types to convert.
+
+    If you specify this parameter, don’t specify --metadata or --source-dir.
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/convert/mdapi.ts)_
+
+## `sf project convert source`
+
+Convert source-formatted files into metadata that you can deploy using Metadata API.
+
+```
+USAGE
+  $ sf project convert source [--json] [--api-version <value>] [-r <value>] [-d <value>] [-n <value>] [-p <value> | -x
+    <value> | -m <value>]
+
+FLAGS
+  -d, --output-dir=<value>     [default: metadataPackage_1695869285197] Output directory to store the Metadata
+                               API–formatted files in.
+  -m, --metadata=<value>...    Metadata component names to convert.
+  -n, --package-name=<value>   Name of the package to associate with the metadata-formatted files.
+  -p, --source-dir=<value>...  Paths to the local source files to convert.
+  -r, --root-dir=<value>       Source directory other than the default package to convert.
+  -x, --manifest=<value>       Path to the manifest (package.xml) file that specifies the metadata types to convert.
+  --api-version=<value>        API Version to use in the generated project's manifest. By default, will use the version
+                               from sfdx-project.json
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Convert source-formatted files into metadata that you can deploy using Metadata API.
+
+  To convert source-formatted files into the metadata format, so that you can deploy them using Metadata API, run this
+  command. Then deploy the metadata using "sf project deploy".
+
+  To convert Metadata API–formatted files into the source format, run "sf project convert mdapi".
+
+  To specify a package name that includes spaces, enclose the name in single quotes.
+
+  To convert multiple components, either set multiple --metadata <name> flags or a single --metadata flag with multiple
+  names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to
+  --manifest and --source-dir.
+
+ALIASES
+  $ sf force source convert
+
+EXAMPLES
+  Convert source-formatted files in the specified directory into metadata-formatted files; writes converted files into
+  a new directory:
+
+    $ sf project convert source --root-dir path/to/source
+
+  Similar to previous example, but writes converted files to the specified output directory and associates the files
+  with the specified package:
+
+    $ sf project convert source --root-dir path/to/source --output-dir path/to/outputdir --package-name 'My Package'
+
+FLAG DESCRIPTIONS
+  -p, --source-dir=<value>...  Paths to the local source files to convert.
+
+    The supplied paths can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all metadata types in the directory and its sub-directories).
+
+    If you specify this parameter, don’t specify --manifest or --metadata.
+
+  -x, --manifest=<value>  Path to the manifest (package.xml) file that specifies the metadata types to convert.
+
+    If you specify this parameter, don’t specify --metadata or --source-dir.
+
+  --api-version=<value>
+
+    API Version to use in the generated project's manifest. By default, will use the version from sfdx-project.json
+
+    Override the api version used for api requests made by this command
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/convert/source.ts)_
+
+## `sf project delete source`
+
+Delete source from your project and from a non-source-tracked org.
+
+```
+USAGE
+  $ sf project delete source -o <value> [--json] [--api-version <value>] [-w <value>] [--tests <value> -l
+    NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [-r] [-m <value>] [-p <value>] [-f [-t | -c]]
+    [--verbose]
+
+FLAGS
+  -c, --check-only             Validate delete command but don't delete anything from the org or the local project.
+  -f, --force-overwrite        Ignore conflict warnings and overwrite changes to the org.
+  -m, --metadata=<value>...    Metadata components to delete.
+  -o, --target-org=<value>     (required) Username or alias of the target org.
+  -p, --source-dir=<value>...  Source file paths to delete.
+  -r, --no-prompt              Don't prompt for delete confirmation.
+  -t, --track-source           If the delete succeeds, update the source tracking information.
+  -w, --wait=<value>           [default: [object Object]] Number of minutes to wait for the command to finish.
+  --api-version=<value>        Override the api version used for api requests made by this command
+  --verbose                    Verbose output of the delete result.
+
+TEST FLAGS
+  -l, --test-level=<option>  Deployment Apex testing level.
+                             <options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
+  --tests=<value>...         Apex tests to run when --test-level is RunSpecifiedTests.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Delete source from your project and from a non-source-tracked org.
+
+  Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs
+  that have source tracking enabled, "sf project deploy start".
+
+  When you run this command, both the local source file and the metadata component in the org are deleted.
+
+  To delete multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with
+  multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax
+  applies to --manifest and --source-dir.
+
+ALIASES
+  $ sf force source delete
+
+EXAMPLES
+  Delete all local Apex source files and all Apex classes from the org with alias "my-scratch":
+
+    $ sf project delete source --metadata ApexClass --target-org my-scratch
+
+  Delete a specific Apex class and a Profile that has a space in it from your default org; don't prompt for
+  confirmation:
+
+    $ sf project delete source --metadata ApexClass:MyFabulousApexClass --metadata "Profile: My Profile" --no-prompt
+
+  Run the tests that aren’t in any managed packages as part of the deletion; if the delete succeeds, and the org has
+  source-tracking enabled, update the source tracking information:
+
+    $ sf project delete source --metadata ApexClass --test-level RunLocalTests --track-source
+
+  Delete the Apex source files in a directory and the corresponding components from your default org:
+
+    $ sf project delete source --source-dir force-app/main/default/classes
+
+FLAG DESCRIPTIONS
+  -c, --check-only  Validate delete command but don't delete anything from the org or the local project.
+
+    IMPORTANT: Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained
+    certain terms to avoid any effect on customer implementations.
+
+    Validates the deleted metadata and runs all Apex tests, but prevents the deletion from being saved to the org.
+
+    If you change a field type from Master-Detail to Lookup or vice versa, that change isn’t supported when using the
+    --chec-konly parameter to test a deletion (validation). This kind of change isn’t supported for test deletions to
+    avoid the risk of data loss or corruption. If a change that isn’t supported for test deletions is included in a
+    deletion package, the test deletion fails and issues an error.
+
+    If your deletion package changes a field type from Master-Detail to Lookup or vice versa, you can still validate the
+    changes prior to deploying to Production by performing a full deletion to another test Sandbox. A full deletion
+    includes a validation of the changes as part of the deletion process.
+
+    Note: A Metadata API deletion that includes Master-Detail relationships deletes all detail records in the Recycle
+    Bin in the following cases.
+
+    1. For a deletion with a new Master-Detail field, soft delete (send to the Recycle Bin) all detail records before
+    proceeding to delete the Master-Detail field, or the deletion fails. During the deletion, detail records are
+    permanently deleted from the Recycle Bin and cannot be recovered.
+
+    2. For a deletion that converts a Lookup field relationship to a Master-Detail relationship, detail records must
+    reference a master record or be soft-deleted (sent to the Recycle Bin) for the deletion to succeed. However, a
+    successful deletion permanently deletes any detail records in the Recycle Bin.
+
+  -l, --test-level=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg  Deployment Apex testing level.
+
+    Valid values are:
+
+    - NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as
+    sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.
+
+    - RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ
+    from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75%
+    code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
+    trigger individually and is different than the overall coverage percentage.
+
+    - RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked
+    packages. This test level is the default for production deployments that include Apex classes or triggers.
+
+    - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
+
+    If you don’t specify a test level, the default behavior depends on the contents of your deployment package and
+    target org. For more information, see “Running Tests in a Deployment” in the Metadata API Developer Guide.
+
+  -m, --metadata=<value>...  Metadata components to delete.
+
+    If you specify this parameter, don’t specify --source-dir.
+
+  -p, --source-dir=<value>...  Source file paths to delete.
+
+    The supplied paths can be a single file (in which case the operation is applied to only one file) or a folder (in
+    which case the operation is applied to all metadata types in the directory and its sub-directories).
+
+    If you specify this parameter, don’t specify --metadata.
+
+  -w, --wait=<value>  Number of minutes to wait for the command to finish.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
+
+  --tests=<value>...  Apex tests to run when --test-level is RunSpecifiedTests.
+
+    If a test name contains a space, enclose it in double quotes.
+    For multiple test names, use one of the following formats:
+
+    - Repeat the flag for multiple test names: --tests Test1 --tests Test2 --tests "Test With Space"
+    - Separate the test names with spaces: --tests Test1 Test2 "Test With Space"
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/delete/source.ts)_
+
+## `sf project delete tracking`
+
+Delete all local source tracking information.
+
+```
+USAGE
+  $ sf project delete tracking -o <value> [--json] [--api-version <value>] [-p]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -p, --no-prompt           Don't prompt for source tracking override confirmation.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Delete all local source tracking information.
+
+  WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.
+
+  Deletes all local source tracking information. When you next run 'project deploy preview', Salesforce CLI displays all
+  local and remote files as changed, and any files with the same name are listed as conflicts.
+
+ALIASES
+  $ sf force source tracking clear
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/delete/tracking.ts)_
+
+## `sf project deploy cancel`
+
+Cancel a deploy operation.
+
+```
+USAGE
+  $ sf project deploy cancel [--json] [--async | -w <value>] [-i <value>] [-r]
+
+FLAGS
+  -i, --job-id=<value>   Job ID of the deploy operation you want to cancel.
+  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+  -w, --wait=<minutes>   Number of minutes to wait for the command to complete and display results.
+  --async                Run the command asynchronously.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Cancel a deploy operation.
+
+  Use this command to cancel a deploy operation that hasn't yet completed in the org. Deploy operations include standard
+  deploys, quick deploys, deploy validations, and deploy cancellations.
+
+  Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most
+  recent deploy operation.
+
+ALIASES
+  $ sf deploy metadata cancel
+
+EXAMPLES
+  Cancel a deploy operation using a job ID:
+
+    $ sf project deploy cancel --job-id 0Af0x000017yLUFCA2
+
+  Cancel the most recent deploy operation:
+
+    $ sf project deploy cancel --use-most-recent
+
+FLAG DESCRIPTIONS
+  -i, --job-id=<value>  Job ID of the deploy operation you want to cancel.
+
+    These commands return a job ID if they time out or you specified the --async flag:
+
+    - sf project deploy start
+    - sf project deploy validate
+    - sf project deploy quick
+    - sf project deploy cancel
+
+    The job ID is valid for 10 days from when you started the deploy operation.
+
+  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+
+    For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less.
+    If your most recent deploy operations was more than 3 days ago, this flag won't find a job ID.
+
+  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To
+    resume watching the cancellation, run "sf project deploy resume". To check the status of the cancellation, run "sf
+    project deploy report".
+
+  --async  Run the command asynchronously.
+
+    The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To
+    resume watching the cancellation, run "sf project deploy resume". To check the status of the cancellation, run "sf
+    project deploy report".
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/cancel.ts)_
+
+## `sf project deploy preview`
+
+Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.
+
+```
+USAGE
+  $ sf project deploy preview -o <value> [--json] [-c] [-x <value> | -d <value> | -m <value>]
+
+FLAGS
+  -c, --ignore-conflicts       Don't display conflicts in preview of the deployment.
+  -d, --source-dir=<value>...  Path to the local source files to preview.
+  -m, --metadata=<value>...    Metadata component names to preview.
+  -o, --target-org=<value>     (required) Login username or alias for the target org.
+  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to preview.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.
+
+  You must run this command from within a project.
+
+  The command outputs a table that describes what will happen if you run the "sf project deploy start" command. The
+  table lists the metadata components that will be deployed and deleted. The table also lists the current conflicts
+  between files in your local project and components in the org. Finally, the table lists the files that won't be
+  deployed because they're included in your .forceignore file.
+
+  If your org allows source tracking, then this command displays potential conflicts between the org and your local
+  project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on
+  scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source
+  flag on the "sf org create scratch|sandbox" commands.
+
+  To preview the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single
+  --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double
+  quotes. The same syntax applies to --manifest and --source-dir.
+
+ALIASES
+  $ sf deploy metadata preview
+
+EXAMPLES
+  NOTE: The commands to preview a deployment and actually deploy it use similar flags. We provide a few preview examples here, but see the help for "sf project deploy start" for more examples that you can adapt for previewing.
+
+  Preview the deployment of source files in a directory, such as force-app, to your default org:
+
+    $ sf project deploy preview  --source-dir force-app
+
+  Preview the deployment of all Apex classes to an org with alias "my-scratch":
+
+    $ sf project deploy preview --metadata ApexClass --target-org my-scratch
+
+  Preview deployment of a specific Apex class:
+
+    $ sf project deploy preview --metadata ApexClass:MyApexClass
+
+  Preview deployment of all components listed in a manifest:
+
+    $ sf project deploy preview --manifest path/to/package.xml
+
+FLAG DESCRIPTIONS
+  -c, --ignore-conflicts  Don't display conflicts in preview of the deployment.
+
+    This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as
+    production orgs.
+
+  -d, --source-dir=<value>...  Path to the local source files to preview.
+
+    The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all metadata types in the directory and its subdirectories).
+
+    If you specify this flag, don’t specify --metadata or --manifest.
+
+  -o, --target-org=<value>  Login username or alias for the target org.
+
+    Overrides your default org.
+
+  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to preview.
+
+    All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/preview.ts)_
+
+## `sf project deploy quick`
+
+Quickly deploy a validated deployment to an org.
+
+```
+USAGE
+  $ sf project deploy quick [--json] [--async | -w <value>] [--concise | --verbose] [-i <value>] [-o <value>] [-r] [-a
+    <value>]
+
+FLAGS
+  -a, --api-version=<value>  Target API version for the deploy.
+  -i, --job-id=<value>       Job ID of the deployment you want to quick deploy.
+  -o, --target-org=<value>   Login username or alias for the target org.
+  -r, --use-most-recent      Use the job ID of the most recently validated deployment.
+  -w, --wait=<minutes>       [default: [object Object]] Number of minutes to wait for the command to complete and
+                             display results.
+  --async                    Run the command asynchronously.
+  --concise                  Show concise output of the deploy result.
+  --verbose                  Show verbose output of the deploy result.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Quickly deploy a validated deployment to an org.
+
+  Before you run this command, first create a validated deployment with the "sf project deploy validate" command, which
+  returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command.
+  Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently
+  validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded.
+
+  Executing this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These
+  tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the
+  deployment to your production org take several hours and you don’t want to risk a failed deploy.
+
+  This command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org.
+  This command doesn’t attempt to merge your source with the versions in your org.
+
+ALIASES
+  $ sf deploy metadata quick
+
+EXAMPLES
+  Run a quick deploy to your default org using a job ID:
+
+    $ sf project deploy quick --job-id 0Af0x000017yLUFCA2
+
+  Asynchronously run a quick deploy of the most recently validated deployment to an org with alias "my-prod-org":
+
+    $ sf project deploy quick --async --use-most-recent --target-org my-prod-org
+
+FLAG DESCRIPTIONS
+  -a, --api-version=<value>  Target API version for the deploy.
+
+    Use this flag to override the default API version with the API version of your package.xml file. The default API
+    version is the latest version supported by the CLI.
+
+  -i, --job-id=<value>  Job ID of the deployment you want to quick deploy.
+
+    The job ID is valid for 10 days from when you started the validation.
+
+  -o, --target-org=<value>  Login username or alias for the target org.
+
+    Overrides your default org.
+
+  -r, --use-most-recent  Use the job ID of the most recently validated deployment.
+
+    For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most
+    recent deployment validation was more than 3 days ago, this flag won't find a job ID.
+
+  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To
+    resume watching the deploy, run "sf project deploy resume". To check the status of the deploy, run "sf project
+    deploy report".
+
+  --async  Run the command asynchronously.
+
+    The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To
+    resume watching the deploy, run "sf project deploy resume". To check the status of the deploy, run "sf project
+    deploy report".
+
+ERROR CODES
+  Succeeded (0)          The deploy succeeded.
+  Canceled (1)           The deploy was canceled.
+  Failed (1)             The deploy failed.
+  SucceededPartial (68)  The deploy partially succeeded.
+  InProgress (69)        The deploy is in progress.
+  Pending (69)           The deploy is pending.
+  Canceling (69)         The deploy is being canceled.
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/quick.ts)_
+
+## `sf project deploy report`
+
+Check or poll for the status of a deploy operation.
+
+```
+USAGE
+  $ sf project deploy report [--json] [-o <value>] [-i <value>] [-r] [--coverage-formatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit] [--results-dir
+    <value>] [-w <value>]
+
+FLAGS
+  -i, --job-id=<value>      Job ID of the deploy operation you want to check the status of.
+  -o, --target-org=<value>  Login username or alias for the target org.
+  -r, --use-most-recent     Use the job ID of the most recent deploy operation.
+  -w, --wait=<minutes>      Number of minutes to wait for command to complete and display results.
+
+TEST FLAGS
+  --coverage-formatters=<option>...  Format of the code coverage results.
+                                     <options: clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|t
+                                     ext|text-summary>
+  --junit                            Output JUnit test results.
+  --results-dir=<value>              Output directory for code coverage and JUnit results; defaults to the deploy ID.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Check or poll for the status of a deploy operation.
+
+  Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations.
+
+  Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most
+  recent deploy operation.  If you specify the --wait flag, the command polls for the status every second until the
+  timeout of --wait minutes.  If you don't specify the --wait flag, the command simply checks and displays the status of
+  the deploy; the command doesn't poll for the status.
+
+  You typically don't specify the --target-org flag because the cached job already references the org to which you
+  deployed.  But if you run this command on a computer different than the one from which you deployed, then you must
+  specify the --target-org and it must point to the same org.
+
+  This command doesn't update source tracking information.
+
+ALIASES
+  $ sf deploy metadata report
+
+EXAMPLES
+  Check the status using a job ID:
+
+    $ sf project deploy report --job-id 0Af0x000017yLUFCA2
+
+  Check the status of the most recent deploy operation:
+
+    $ sf project deploy report --use-most-recent
+
+  Poll for the status using a job ID and target org:
+
+    $ sf project deploy report --job-id 0Af0x000017yLUFCA2 --target-org me@my.org --wait 30
+
+FLAG DESCRIPTIONS
+  -i, --job-id=<value>  Job ID of the deploy operation you want to check the status of.
+
+    These commands return a job ID if they time out or you specified the --async flag:
+
+    - sf project deploy start
+    - sf project deploy validate
+    - sf project deploy quick
+    - sf project deploy cancel
+
+    The job ID is valid for 10 days from when you started the deploy operation.
+
+  -o, --target-org=<value>  Login username or alias for the target org.
+
+    Overrides your default org.
+
+  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+
+    For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less.
+    If your most recent operation was more than 3 days ago, this flag won't find a job ID.
+
+  -w, --wait=<minutes>  Number of minutes to wait for command to complete and display results.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
+    returns the job ID. To resume the deployment, run "sf project deploy resume". To check the status of the deployment,
+    run "sf project deploy report".
+
+  --coverage-formatters=clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary...
+
+    Format of the code coverage results.
+
+    For multiple formatters, repeat the flag for each formatter.
+    --coverage-formatters lcov --coverage-formatters clover
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/report.ts)_
+
+## `sf project deploy resume`
+
+Resume watching a deploy operation and update source tracking when the deploy completes.
+
+```
+USAGE
+  $ sf project deploy resume [--json] [--concise | --verbose] [-i <value>] [-r] [-w <value>] [--coverage-formatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit] [--results-dir
+    <value>]
+
+FLAGS
+  -i, --job-id=<value>   Job ID of the deploy operation you want to resume.
+  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+  -w, --wait=<minutes>   Number of minutes to wait for the command to complete and display results.
+  --concise              Show concise output of the deploy operation result.
+  --verbose              Show verbose output of the deploy operation result.
+
+TEST FLAGS
+  --coverage-formatters=<option>...  Format of the code coverage results.
+                                     <options: clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|t
+                                     ext|text-summary>
+  --junit                            Output JUnit test results.
+  --results-dir=<value>              Output directory for code coverage and JUnit results; defaults to the deploy ID.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Resume watching a deploy operation and update source tracking when the deploy completes.
+
+  Use this command to resume watching a deploy operation if the original command times out or you specified the --async
+  flag. Deploy operations include standard deploys, quick deploys, deploy validations, and deploy cancellations. This
+  command doesn't resume the original operation itself, because the operation always continues after you've started it,
+  regardless of whether you're watching it or not. When the deploy completes, source tracking information is updated as
+  needed.
+
+  Run this command by either passing it a job ID or specifying the --use-most-recent flag to use the job ID of the most
+  recent deploy operation.
+
+ALIASES
+  $ sf deploy metadata resume
+
+EXAMPLES
+  Resume watching a deploy operation using a job ID:
+
+    $ sf project deploy resume --job-id 0Af0x000017yLUFCA2
+
+  Resume watching the most recent deploy operation:
+
+    $ sf project deploy resume --use-most-recent
+
+FLAG DESCRIPTIONS
+  -i, --job-id=<value>  Job ID of the deploy operation you want to resume.
+
+    These commands return a job ID if they time out or you specified the --async flag:
+
+    - sf project deploy start
+    - sf project deploy validate
+    - sf project deploy quick
+    - sf project deploy cancel
+
+    The job ID is valid for 10 days from when you started the deploy operation.
+
+  -r, --use-most-recent  Use the job ID of the most recent deploy operation.
+
+    For performance reasons, this flag uses job IDs for deploy operations that started only in the past 3 days or less.
+    If your most recent operation was more than 3 days ago, this flag won't find a job ID.
+
+  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To
+    resume watching the deploy operation, run this command again. To check the status of the deploy operation, run "sf
+    project deploy report".
+
+  --coverage-formatters=clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary...
+
+    Format of the code coverage results.
+
+    For multiple formatters, repeat the flag for each formatter.
+    --coverage-formatters lcov --coverage-formatters clover
+
+ENVIRONMENT VARIABLES
+  SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
+
+ERROR CODES
+  Succeeded (0)          The deploy succeeded.
+  Canceled (1)           The deploy was canceled.
+  Failed (1)             The deploy failed.
+  SucceededPartial (68)  The deploy partially succeeded.
+  InProgress (69)        The deploy is in progress.
+  Pending (69)           The deploy is pending.
+  Canceling (69)         The deploy is being canceled.
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/resume.ts)_
+
+## `sf project deploy start`
+
+Deploy metadata to an org from your local project.
+
+```
+USAGE
+  $ sf project deploy start -o <value> [--json] [-a <value>] [--async | -w <value>] [--concise | --verbose] [--dry-run]
+    [-c] [-r] [-g] [--single-package ] [-t <value> -l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg]
+    [--purge-on-delete [-x <value> | -d <value> | -m <value> | --metadata-dir <value>]] [--pre-destructive-changes
+    <value> ] [--post-destructive-changes <value> ] [--coverage-formatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit] [--results-dir
+    <value>]
+
+FLAGS
+  -a, --api-version=<value>  Target API version for the deploy.
+  -c, --ignore-conflicts     Ignore conflicts and deploy local files, even if they overwrite changes in the org.
+  -g, --ignore-warnings      Ignore warnings and allow a deployment to complete successfully.
+  -o, --target-org=<value>   (required) Login username or alias for the target org.
+  -r, --ignore-errors        Ignore any errors and don’t roll back deployment.
+  -w, --wait=<minutes>       [default: [object Object]] Number of minutes to wait for command to complete and display
+                             results.
+  --async                    Run the command asynchronously.
+  --concise                  Show concise output of the deploy result.
+  --dry-run                  Validate deploy and run Apex tests but don’t save to the org.
+  --verbose                  Show verbose output of the deploy result.
+
+SOURCE FORMAT FLAGS
+  -d, --source-dir=<value>...  Path to the local source files to deploy.
+  -m, --metadata=<value>...    Metadata component names to deploy. Wildcards ( * ) supported as long as you use quotes,
+                               such as 'ApexClass:MyClass*'
+  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to deploy.
+
+TEST FLAGS
+  -l, --test-level=<option>          Deployment Apex testing level.
+                                     <options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
+  -t, --tests=<value>...             Apex tests to run when --test-level is RunSpecifiedTests.
+  --coverage-formatters=<option>...  Format of the code coverage results.
+                                     <options: clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|t
+                                     ext|text-summary>
+  --junit                            Output JUnit test results.
+  --results-dir=<value>              Output directory for code coverage and JUnit results; defaults to the deploy ID.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+METADATA API FORMAT FLAGS
+  --metadata-dir=<value>  Root of directory or zip file of metadata formatted files to deploy.
+  --single-package        Indicates that the metadata zip file points to a directory structure for a single package.
+
+DELETE FLAGS
+  --post-destructive-changes=<value>  File path for a manifest (destructiveChangesPost.xml) of components to delete
+                                      after the deploy.
+  --pre-destructive-changes=<value>   File path for a manifest (destructiveChangesPre.xml) of components to delete
+                                      before the deploy
+  --purge-on-delete                   Specify that deleted components in the destructive changes manifest file are
+                                      immediately eligible for deletion rather than being stored in the Recycle Bin.
+
+DESCRIPTION
+  Deploy metadata to an org from your local project.
+
+  You must run this command from within a project.
+
+  Metadata components are deployed in source format by default. Deploy them in metadata format by specifying the
+  --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you
+  want to deploy.
+
+  If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production
+  org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable
+  source tracking when you create the orgs by specifying the --no-track-source flag on the "sf org create
+  scratch|sandbox" commands.
+
+  To deploy multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with
+  multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax
+  applies to --manifest and --source-dir.
+
+ALIASES
+  $ sf deploy metadata
+
+EXAMPLES
+  Deploy local changes not in the org; uses your default org:
+
+    $ sf project deploy start
+
+  Deploy the source files in a directory to an org with alias "my-scratch":
+
+    $ sf project deploy start  --source-dir path/to/source --target-org my-scratch
+
+  Deploy a specific Apex class and the objects whose source is in a directory (both examples are equivalent):
+
+    $ sf project deploy start --source-dir path/to/apex/classes/MyClass.cls path/to/source/objects
+    $ sf project deploy start --source-dir path/to/apex/classes/MyClass.cls --source-dir path/to/source/objects
+
+  Deploy all Apex classes:
+
+    $ sf project deploy start --metadata ApexClass
+
+  Deploy a specific Apex class:
+
+    $ sf project deploy start --metadata ApexClass:MyApexClass
+
+  Deploy specific Apex classes that match a pattern; in this example, deploy Apex classes whose names contain the
+  string "MyApex":
+
+    $ sf project deploy start --metadata 'ApexClass:MyApex*'
+
+  Deploy all custom objects and Apex classes (both examples are equivalent):
+
+    $ sf project deploy start --metadata CustomObject ApexClass
+    $ sf project deploy start --metadata CustomObject --metadata ApexClass
+
+  Deploy all Apex classes and a profile that has a space in its name:
+
+    $ sf project deploy start --metadata ApexClass --metadata "Profile:My Profile"
+
+  Deploy all components listed in a manifest:
+
+    $ sf project deploy start --manifest path/to/package.xml
+
+  Run the tests that aren’t in any managed packages as part of a deployment:
+
+    $ sf project deploy start --metadata ApexClass --test-level RunLocalTests
+
+FLAG DESCRIPTIONS
+  -a, --api-version=<value>  Target API version for the deploy.
+
+    Use this flag to override the default API version with the API version of your package.xml file. The default API
+    version is the latest version supported by the CLI.
+
+  -c, --ignore-conflicts  Ignore conflicts and deploy local files, even if they overwrite changes in the org.
+
+    This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as
+    production orgs.
+
+  -d, --source-dir=<value>...  Path to the local source files to deploy.
+
+    The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all metadata types in the directory and its subdirectories).
+
+    If you specify this flag, don’t specify --metadata or --manifest.
+
+  -g, --ignore-warnings  Ignore warnings and allow a deployment to complete successfully.
+
+    If a warning occurs and this flag is set to true, the success status of the deployment is set to true. When this
+    flag is set to false, success is set to false, and the warning is treated like an error.
+
+  -l, --test-level=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg  Deployment Apex testing level.
+
+    Valid values are:
+
+    - NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as
+    sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.
+
+    - RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ
+    from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75%
+    code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
+    trigger individually and is different than the overall coverage percentage.
+
+    - RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked
+    packages. This test level is the default for production deployments that include Apex classes or triggers.
+
+    - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
+
+    If you don’t specify a test level, the default behavior depends on the contents of your deployment package and
+    target org. For more information, see [Running Tests in a
+    Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)
+    in the "Metadata API Developer Guide".
+
+  -o, --target-org=<value>  Login username or alias for the target org.
+
+    Overrides your default org.
+
+  -r, --ignore-errors  Ignore any errors and don’t roll back deployment.
+
+    When deploying to a production org, keep this flag set to false (default value). When set to true, components
+    without errors are deployed and components with errors are skipped, and could result in an inconsistent production
+    org.
+
+  -t, --tests=<value>...  Apex tests to run when --test-level is RunSpecifiedTests.
+
+    If a test name contains a space, enclose it in double quotes.
+    For multiple test names, use one of the following formats:
+
+    - Repeat the flag for multiple test names: --tests Test1 --tests Test2 --tests "Test With Space"
+    - Separate the test names with spaces: --tests Test1 Test2 "Test With Space"
+
+  -w, --wait=<minutes>  Number of minutes to wait for command to complete and display results.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
+    returns the job ID. To resume the deployment, run "sf project deploy resume". To check the status of the deployment,
+    run "sf project deploy report".
+
+  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to deploy.
+
+    All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
+
+  --async  Run the command asynchronously.
+
+    The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the
+    CLI. To resume the deployment, run "sf project deploy resume". To check the status of the deployment, run "sf
+    project deploy report".
+
+  --coverage-formatters=clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary...
+
+    Format of the code coverage results.
+
+    For multiple formatters, repeat the flag for each formatter.
+    --coverage-formatters lcov --coverage-formatters clover
+
+CONFIGURATION VARIABLES
+  target-org       Username or alias of the org that all commands run against by default. (sf only)
+  org-api-version  API version of your project. Default: API version of your Dev Hub org.
+
+ENVIRONMENT VARIABLES
+  SF_TARGET_ORG        Username or alias of your default org. Overrides the target-org configuration variable.
+  SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
+
+ERROR CODES
+  Succeeded (0)          The deploy succeeded.
+  Canceled (1)           The deploy was canceled.
+  Failed (1)             The deploy failed.
+  SucceededPartial (68)  The deploy partially succeeded.
+  InProgress (69)        The deploy is in progress.
+  Pending (69)           The deploy is pending.
+  Canceling (69)         The deploy is being canceled.
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/start.ts)_
+
+## `sf project deploy validate`
+
+Validate a metadata deployment without actually executing it.
+
+```
+USAGE
+  $ sf project deploy validate -o <value> [--json] [-a <value>] [--async] [--concise | --verbose] [-m <value>] [-d <value>]
+    [--single-package --metadata-dir <value>] [-t <value> -l RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests] [-w
+    <value>] [--coverage-formatters
+    clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary] [--junit] [--results-dir
+    <value>] [--purge-on-delete -x <value>] [--pre-destructive-changes <value> ] [--post-destructive-changes <value> ]
+
+FLAGS
+  -a, --api-version=<value>  Target API version for the validation.
+  -o, --target-org=<value>   (required) Login username or alias for the target org.
+  -w, --wait=<minutes>       [default: [object Object]] Number of minutes to wait for the command to complete and
+                             display results.
+  --async                    Run the command asynchronously.
+  --concise                  Show concise output of the validation result.
+  --verbose                  Show verbose output of the validation result.
+
+SOURCE FORMAT FLAGS
+  -d, --source-dir=<value>...  Path to the local source files to validate for deployment.
+  -m, --metadata=<value>...    Metadata component names to validate for deployment.
+  -x, --manifest=<value>       Full file path for manifest (package.xml) of components to validate for deployment.
+
+TEST FLAGS
+  -l, --test-level=<option>          [default: RunLocalTests] Deployment Apex testing level.
+                                     <options: RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests>
+  -t, --tests=<value>...             Apex tests to run when --test-level is RunSpecifiedTests.
+  --coverage-formatters=<option>...  Format of the code coverage results.
+                                     <options: clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|t
+                                     ext|text-summary>
+  --junit                            Output JUnit test results.
+  --results-dir=<value>              Output directory for code coverage and JUnit results; defaults to the deploy ID.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+METADATA API FORMAT FLAGS
+  --metadata-dir=<value>  Root of directory or zip file of metadata formatted files to deploy.
+  --single-package        Indicates that the metadata zip file points to a directory structure for a single package.
+
+DELETE FLAGS
+  --post-destructive-changes=<value>  File path for a manifest (destructiveChangesPost.xml) of components to delete
+                                      after the deploy.
+  --pre-destructive-changes=<value>   File path for a manifest (destructiveChangesPre.xml) of components to delete
+                                      before the deploy
+  --purge-on-delete                   Specify that deleted components in the destructive changes manifest file are
+                                      immediately eligible for deletion rather than being stored in the Recycle Bin.
+
+DESCRIPTION
+  Validate a metadata deployment without actually executing it.
+
+  Use this command to verify whether a deployment will succeed without actually deploying the metadata to your org. This
+  command is similar to "sf project deploy start", except you're required to run Apex tests, and the command returns a
+  job ID rather than executing the deployment. If the validation succeeds, then you pass this job ID to the "sf project
+  deploy quick" command to actually deploy the metadata. This quick deploy takes less time because it skips running Apex
+  tests. The job ID is valid for 10 days from when you started the validation. Validating first is useful if the
+  deployment to your production org take several hours and you don’t want to risk a failed deploy.
+
+  You must run this command from within a project.
+
+  This command doesn't support source-tracking. When you quick deploy with the resulting job ID, the source you deploy
+  overwrites the corresponding metadata in your org.
+
+  To validate the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single
+  --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double
+  quotes. The same syntax applies to --manifest and --source-dir.
+
+ALIASES
+  $ sf deploy metadata validate
+
+EXAMPLES
+  NOTE: These examples focus on validating large deployments. See the help for "sf project deploy start" for examples of deploying smaller sets of metadata which you can also use to validate.
+
+  Validate the deployment of all source files in a directory to the default org:
+
+    $ sf project deploy validate --source-dir path/to/source
+
+  Asynchronously validate the deployment and run all tests in the org with alias "my-prod-org"; command immediately
+  returns the job ID:
+
+    $ sf project deploy validate --source-dir path/to/source --async --test-level RunAllTestsInOrg --target-org \
+      my-prod-org
+
+  Validate the deployment of all components listed in a manifest:
+
+    $ sf project deploy validate --manifest path/to/package.xml
+
+FLAG DESCRIPTIONS
+  -a, --api-version=<value>  Target API version for the validation.
+
+    Use this flag to override the default API version with the API version of your package.xml file. The default API
+    version is the latest version supported by the CLI.
+
+  -d, --source-dir=<value>...  Path to the local source files to validate for deployment.
+
+    The supplied path can be to a single file (in which case the operation is applied to only one file) or to a folder
+    (in which case the operation is applied to all metadata types in the directory and its subdirectories).
+
+    If you specify this flag, don’t specify --metadata or --manifest.
+
+  -l, --test-level=RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests  Deployment Apex testing level.
+
+    Valid values are:
+
+    - RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ
+    from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75%
+    code coverage for each class and trigger in the deployment package. This coverage is computed for each class and
+    trigger individually and is different than the overall coverage percentage.
+
+    - RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked
+    packages. This test level is the default.
+
+    - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
+
+  -o, --target-org=<value>  Login username or alias for the target org.
+
+    Overrides your default org.
+
+  -t, --tests=<value>...  Apex tests to run when --test-level is RunSpecifiedTests.
+
+    If a test name contains a space, enclose it in double quotes.
+    For multiple test names, use one of the following formats:
+
+    - Repeat the flag for multiple test names: --tests Test1 --tests Test2 --tests "Test With Space"
+    - Separate the test names with spaces: --tests Test1 Test2 "Test With Space"
+
+  -w, --wait=<minutes>  Number of minutes to wait for the command to complete and display results.
+
+    If the command continues to run after the wait period, the CLI returns control of the terminal window to you and
+    returns the job ID. To resume watching the validation, run "sf project deploy resume". To check the status of the
+    validation, run "sf project deploy report".
+
+  -x, --manifest=<value>  Full file path for manifest (package.xml) of components to validate for deployment.
+
+    All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
+
+  --async  Run the command asynchronously.
+
+    The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the
+    CLI. To resume watching the validation, run "sf project deploy resume". To check the status of the validation, run
+    "sf project deploy report".
+
+  --coverage-formatters=clover|cobertura|html-spa|html|json|json-summary|lcovonly|none|teamcity|text|text-summary...
+
+    Format of the code coverage results.
+
+    For multiple formatters, repeat the flag for each formatter.
+    --coverage-formatters lcov --coverage-formatters clover
+
+CONFIGURATION VARIABLES
+  target-org       Username or alias of the org that all commands run against by default. (sf only)
+  org-api-version  API version of your project. Default: API version of your Dev Hub org.
+
+ENVIRONMENT VARIABLES
+  SF_TARGET_ORG        Username or alias of your default org. Overrides the target-org configuration variable.
+  SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
+
+ERROR CODES
+  Succeeded (0)          The deploy succeeded.
+  Canceled (1)           The deploy was canceled.
+  Failed (1)             The deploy failed.
+  SucceededPartial (68)  The deploy partially succeeded.
+  InProgress (69)        The deploy is in progress.
+  Pending (69)           The deploy is pending.
+  Canceling (69)         The deploy is being canceled.
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/deploy/validate.ts)_
+
+## `sf project generate`
+
+Generate a Salesforce DX project.
+
+```
+USAGE
+  $ sf project generate -n <value> [--json] [-t standard|empty|analytics] [-d <value>] [-s <value>] [-p <value>] [-x]
+    [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>           [default: .] Directory for saving the created files.
+  -n, --name=<value>                 (required) Name of the generated project.
+  -p, --default-package-dir=<value>  [default: force-app] Default package directory name.
+  -s, --namespace=<value>            Namespace associated with this project and any connected scratch orgs.
+  -t, --template=<option>            [default: standard] Template to use for project creation.
+                                     <options: standard|empty|analytics>
+  -x, --manifest                     Generate a manifest (package.xml) for change-set based development.
+  --api-version=<value>              Will set this version as sourceApiVersion in the sfdx-project.json file
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Generate a Salesforce DX project.
+
+  A Salesforce DX project has a specific structure and a configuration file (sfdx-project.json) that identifies the
+  directory as a Salesforce DX project. This command generates the necessary configuration files and directories to get
+  you started.
+
+  By default, the generated sfdx-project.json file sets the sourceApiVersion property to the default API version
+  currently used by Salesforce CLI. To specify a different version, set the apiVersion configuration variable. For
+  example: "sf config set apiVersion=57.0 --global".
+
+ALIASES
+  $ sf force project create
+
+EXAMPLES
+  Generate a project called "mywork":
+
+    $ sf project generate --name mywork
+
+  Similar to previous example, but generate the files in a directory called "myapp":
+
+    $ sf project generate --name mywork --default-package-dir myapp
+
+  Similar to prevoius example, but also generate a default package.xml manifest file:
+
+    $ sf project generate --name mywork --default-package-dir myapp --manifest
+
+  Generate a project with the minimum files and directories:
+
+    $ sf project generate --name mywork --template empty
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated project.
+
+    Generates a project directory with this name; any valid directory name is accepted. Also sets the "name" property in
+    the sfdx-project.json file to this name.
+
+  -p, --default-package-dir=<value>  Default package directory name.
+
+    Metadata items such as classes and Lightning bundles are placed inside this folder.
+
+  -t, --template=standard|empty|analytics  Template to use for project creation.
+
+    The template determines the sample configuration files and directories that this command generates. For example, the
+    empty template provides these files and directory to get you started.
+
+    - .forceignore
+    - config/project-scratch-def.json
+    - sfdx-project.json
+    - package.json
+    - force-app (basic source directory structure)
+
+    The standard template provides a complete force-app directory structure so you know where to put your source. It
+    also provides additional files and scripts, especially useful when using Salesforce Extensions for VS Code. For
+    example:
+
+    - .gitignore: Use Git for version control.
+    - .prettierrc and .prettierignore: Use Prettier to format your Aura components.
+    - .vscode/extensions.json: When launched, Visual Studio Code, prompts you to install the recommended extensions for
+    your project.
+    - .vscode/launch.json: Configures Replay Debugger.
+    - .vscode/settings.json: Additional configuration settings.
+
+    The analytics template provides similar files and the force-app/main/default/waveTemplates directory.
+
+  -x, --manifest  Generate a manifest (package.xml) for change-set based development.
+
+    Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static
+    resources.
+
+  --api-version=<value>  Will set this version as sourceApiVersion in the sfdx-project.json file
+
+    Override the api version used for api requests made by this command
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/project/generate.ts)_
+
+## `sf project generate manifest`
+
+Create a project manifest that lists the metadata components you want to deploy or retrieve.
+
+```
+USAGE
+  $ sf project generate manifest [--json] [--api-version <value>] [-m <value>] [-p <value>] [-n <value> | -t
+    pre|post|destroy|package] [-c managed|unlocked --from-org <value>] [-d <value>]
+
+FLAGS
+  -c, --include-packages=<option>...  Package types (managed, unlocked) whose metadata is included in the manifest; by
+                                      default, metadata in packages is ignored.
+                                      <options: managed|unlocked>
+  -d, --output-dir=<value>            Directory to save the created manifest.
+  -m, --metadata=<value>...           Names of metadata components to include in the manifest.
+  -n, --name=<value>                  Name of a custom manifest file to create.
+  -p, --source-dir=<value>...         Paths to the local source files to include in the manifest.
+  -t, --type=<option>                 Type of manifest to create; the type determines the name of the created file.
+                                      <options: pre|post|destroy|package>
+  --api-version=<value>               Override the api version used for api requests made by this command
+  --from-org=<value>                  Username or alias of the org that contains the metadata components from which to
+                                      build a manifest.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Create a project manifest that lists the metadata components you want to deploy or retrieve.
+
+  Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain
+  source files (--source-dir). You can specify either of these parameters, not both.
+
+  Use --type to specify the type of manifest you want to create. The resulting manifest files have specific names, such
+  as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their
+  respective file names, are:
+
+  * package : package.xml (default)
+  * pre : destructiveChangesPre.xml
+  * post : destructiveChangesPost.xml
+  * destroy : destructiveChanges.xml
+
+  See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for
+  information about these destructive manifest files.
+
+  Use --name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can
+  specify either --type or --name, but not both.
+
+  To include multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with
+  multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax
+  applies to --include-packages and --source-dir.
+
+ALIASES
+  $ sf force source manifest create
+
+EXAMPLES
+  Create a manifest for deploying or retrieving all Apex classes and custom objects:
+
+    $ sf project generate manifest --metadata ApexClass --metadata CustomObject
+
+  Create a manifest for deleting the specified Apex class:
+
+    $ sf project generate manifest --metadata ApexClass:MyApexClass --type destroy
+
+  Create a manifest for deploying or retrieving all the metadata components in the specified local directory; name the
+  file myNewManifest.xml:
+
+    $ sf project generate manifest --source-dir force-app --name myNewManifest
+
+  Create a manifest from the metadata components in the specified org and include metadata in any unlocked packages:
+
+    $ sf project generate manifest --from-org test@myorg.com --include-packages unlocked
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/generate/manifest.ts)_
+
+## `sf project list ignored`
+
+Check your local project package directories for forceignored files.
+
+```
+USAGE
+  $ sf project list ignored [--json] [-p <value>]
+
+FLAGS
+  -p, --source-dir=<value>  File or directory of files that the command checks for foreceignored files.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Check your local project package directories for forceignored files.
+
+  When deploying or retrieving metadata between your local project and an org, you can specify the source files you want
+  to exclude with a .forceignore file. The .forceignore file structure mimics the .gitignore structure. Each line in
+  .forceignore specifies a pattern that corresponds to one or more files. The files typically represent metadata
+  components, but can be any files you want to exclude, such as LWC configuration JSON files or tests.
+
+ALIASES
+  $ sf force source ignored list
+
+EXAMPLES
+  List all the files in all package directories that are ignored:
+
+    $ sf project list ignored
+
+  List all the files in a specific directory that are ignored:
+
+    $ sf project list ignored --source-dir force-app
+
+  Check if a particular file is ignored:
+
+    $ sf project list ignored --source-dir package.xml
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/list/ignored.ts)_
+
+## `sf project reset tracking`
+
+Reset local and remote source tracking.
+
+```
+USAGE
+  $ sf project reset tracking -o <value> [--json] [--api-version <value>] [-r <value>] [-p]
+
+FLAGS
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -p, --no-prompt           Don't prompt for source tracking override confirmation.
+  -r, --revision=<value>    SourceMember revision counter number to reset to.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Reset local and remote source tracking.
+
+  WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.
+
+  Resets local and remote source tracking so that Salesforce CLI no longer registers differences between your local
+  files and those in the org. When you next run 'project deploy preview', Salesforce CLI returns no results, even though
+  conflicts might actually exist. Salesforce CLI then resumes tracking new source changes as usual.
+
+  Use the --revision parameter to reset source tracking to a specific revision number of an org source member. To get
+  the revision number, query the SourceMember Tooling API object with the 'data soql' command. For example:
+
+  sf data query --query "SELECT MemberName, MemberType, RevisionCounter FROM SourceMember" --use-tooling-api
+
+ALIASES
+  $ sf force source tracking reset
+```
+
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/reset/tracking.ts)_
+
+## `sf project retrieve preview`
+
+Preview a retrieval to see what will be retrieved from the org, the potential conflicts, and the ignored files.
 
 ```
 USAGE
-  $ sf plugins:uninstall PLUGIN...
-
-ARGUMENTS
-  PLUGIN  plugin to uninstall
+  $ sf project retrieve preview -o <value> [--json] [-c]
 
 FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
+  -c, --ignore-conflicts    Don't display conflicts in the preview of the retrieval.
+  -o, --target-org=<value>  (required) Login username or alias for the target org.
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Removes a plugin from the CLI.
+  Preview a retrieval to see what will be retrieved from the org, the potential conflicts, and the ignored files.
+
+  You must run this command from within a project.
+
+  The command outputs a table that describes what will happen if you run the "sf project retrieve start" command. The
+  table lists the metadata components that will be retrieved and deleted. The table also lists the current conflicts
+  between files in your local project and components in the org. Finally, the table lists the files that won't be
+  retrieved because they're included in your .forceignore file.
+
+  If your org allows source tracking, then this command displays potential conflicts between the org and your local
+  project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on
+  scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source
+  flag on the "sf org create scratch|sandbox" commands.
 
 ALIASES
-  $ sf plugins unlink
-  $ sf plugins remove
-```
+  $ sf retrieve metadata preview
 
-## `sf plugins update`
+EXAMPLES
+  Preview the retrieve of all changes from your default org:
 
-Update installed plugins.
+    $ sf project retrieve preview
 
-```
-USAGE
-  $ sf plugins update [-h] [-v]
+  Preview the retrieve when ignoring any conflicts from an org with alias "my-scratch":
 
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
+    $ sf project retrieve preview --ignore-conflicts --target-org my-scratch
 
-DESCRIPTION
-  Update installed plugins.
+FLAG DESCRIPTIONS
+  -c, --ignore-conflicts  Don't display conflicts in the preview of the retrieval.
+
+    This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as
+    production orgs.
+
+  -o, --target-org=<value>  Login username or alias for the target org.
+
+    Overrides your default org.
 ```
 
-## `sf retrieve metadata`
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/retrieve/preview.ts)_
+
+## `sf project retrieve start`
 
 Retrieve metadata from an org to your local project.
 
 ```
 USAGE
-  $ sf retrieve metadata [--json] [-a <value>] [-c] [-x <value> | -m <value> | -d <value>] [-n <value>]
-    [--single-package -t <value>] [-o <value>] [-w <value>] [-z ] [--zip-file-name <value> ]
+  $ sf project retrieve start -o <value> [--json] [-a <value>] [-c] [-x <value> | -m <value> | -d <value>] [-r <value> | -n
+    <value> | ] [--single-package -t <value>] [-w <value>] [-z ] [--zip-file-name <value> ]
 
 FLAGS
-  -a, --api-version=<value>          Target API version for the retrieve.
-  -c, --ignore-conflicts             Ignore conflicts and retrieve and save files to your local filesystem, even if they
-                                     overwrite your local changes.
-  -d, --source-dir=<value>...        File paths for source to retrieve from the org.
-  -m, --metadata=<value>...          Metadata component names to retrieve.
-  -n, --package-name=<value>...      Package names to retrieve.
-  -o, --target-org=<value>           Login username or alias for the target org.
+  -a, --api-version=<value>      Target API version for the retrieve.
+  -c, --ignore-conflicts         Ignore conflicts and retrieve and save files to your local filesystem, even if they
+                                 overwrite your local changes.
+  -d, --source-dir=<value>...    File paths for source to retrieve from the org.
+  -m, --metadata=<value>...      Metadata component names to retrieve. Wildcards ( * ) supported as long as you use
+                                 quotes, such as 'ApexClass:MyClass*'
+  -n, --package-name=<value>...  Package names to retrieve.
+  -o, --target-org=<value>       (required) Login username or alias for the target org.
+  -r, --output-dir=<value>       Directory root for the retrieved source files.
+  -w, --wait=<value>             [default: [object Object]] Number of minutes to wait for the command to complete and
+                                 display results to the terminal window.
+  -x, --manifest=<value>         File path for the manifest (package.xml) that specifies the components to retrieve.
+
+METADATA API FORMAT FLAGS
   -t, --target-metadata-dir=<value>  Directory that will contain the retrieved metadata format files or ZIP.
-  -w, --wait=<value>                 Number of minutes to wait for the command to complete and display results to the
-                                     terminal window.
-  -x, --manifest=<value>             File path for the manifest (package.xml) that specifies the components to retrieve.
   -z, --unzip                        Extract all files from the retrieved zip file.
   --single-package                   Indicates that the zip file points to a directory structure for a single package.
   --zip-file-name=<value>            File name to use for the retrieved zip file.
@@ -2873,61 +6762,71 @@ DESCRIPTION
   --target-metadata-dir flag, which retrieves the components into a ZIP file in the specified directory.
 
   If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production
-  org, never allow source tracking. You can also use the "--no-track-source" flag when you create a scratch or sandbox
-  org to disable source tracking.
+  org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable
+  source tracking when you create the orgs by specifying the --no-track-source flag on the "sf org create
+  scratch|sandbox" commands.
 
   To retrieve multiple metadata components, either use multiple --metadata <name> flags or use a single --metadata flag
   with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same
   syntax applies to --manifest and --source-dir.
 
+ALIASES
+  $ sf retrieve metadata
+
 EXAMPLES
-  Retrieve remote changes:
+  Retrieve remote changes from your default org:
 
-    $ sf retrieve metadata
+    $ sf project retrieve start
 
-  Retrieve the source files in a directory:
+  Retrieve the source files in a directory from an org with alias "my-scratch":
 
-    $ sf retrieve metadata --source-dir path/to/source
+    $ sf project retrieve start --source-dir path/to/source --target-org my-scratch
 
   Retrieve a specific Apex class and the objects whose source is in a directory (both examples are equivalent):
 
-    $ sf retrieve metadata --source-dir path/to/apex/classes/MyClass.cls path/to/source/objects
-    $ sf retrieve metadata --source-dir path/to/apex/classes/MyClass.cls --source-dir path/to/source/objects
+    $ sf project retrieve start --source-dir path/to/apex/classes/MyClass.cls path/to/source/objects
+    $ sf project retrieve start --source-dir path/to/apex/classes/MyClass.cls --source-dir path/to/source/objects
 
   Retrieve all Apex classes:
 
-    $ sf retrieve metadata --metadata ApexClass
+    $ sf project retrieve start --metadata ApexClass
 
   Retrieve a specific Apex class:
 
-    $ sf retrieve metadata --metadata ApexClass:MyApexClass
+    $ sf project retrieve start --metadata ApexClass:MyApexClass
+
+  Retrieve specific Apex classes that match a pattern; in this example, retrieve Apex classes whose names contain the
+  string "MyApex":
+
+    $ sf project retrieve start --metadata 'ApexClass:MyApex*'
 
   Retrieve all custom objects and Apex classes (both examples are equivalent):
 
-    $ sf retrieve metadata --metadata CustomObject ApexClass
-    $ sf retrieve metadata --metadata CustomObject --metadata ApexClass
+    $ sf project retrieve start --metadata CustomObject ApexClass
+    $ sf project retrieve start --metadata CustomObject --metadata ApexClass
 
   Retrieve all metadata components listed in a manifest:
 
-    $ sf retrieve metadata --manifest path/to/package.xml
+    $ sf project retrieve start --manifest path/to/package.xml
 
   Retrieve metadata from a package:
 
-    $ sf retrieve metadata --package-name MyPackageName
+    $ sf project retrieve start --package-name MyPackageName
 
   Retrieve metadata from multiple packages, one of which has a space in its name (both examples are equivalent):
 
-    $ sf retrieve metadata --package-name Package1 "PackageName With Spaces" Package3
-    $ sf retrieve metadata --package-name Package1 --package-name "PackageName With Spaces" --package-name Package3
+    $ sf project retrieve start --package-name Package1 "PackageName With Spaces" Package3
+    $ sf project retrieve start --package-name Package1 --package-name "PackageName With Spaces" --package-name \
+      Package3
 
   Retrieve the metadata components listed in the force-app directory, but retrieve them in metadata format into a ZIP
   file in the "output" directory:
 
-    $ sf retrieve metadata --source-dir force-app --target-metadata-dir output
+    $ sf project retrieve start --source-dir force-app --target-metadata-dir output
 
   Retrieve in metadata format and automatically extract the contents into the "output" directory:
 
-    $ sf retrieve metadata --source-dir force-app --target-metadata-dir output --unzip
+    $ sf project retrieve start --source-dir force-app --target-metadata-dir output --unzip
 
 FLAG DESCRIPTIONS
   -a, --api-version=<value>  Target API version for the retrieve.
@@ -2951,6 +6850,12 @@ FLAG DESCRIPTIONS
 
     Overrides your default org.
 
+  -r, --output-dir=<value>  Directory root for the retrieved source files.
+
+    The root of the directory structure into which the source files are retrieved.
+    If the target directory matches one of the package directories in your sfdx-project.json file, the command fails.
+    Running the command multiple times with the same target adds new files and overwrites existing files.
+
   -w, --wait=<value>  Number of minutes to wait for the command to complete and display results to the terminal window.
 
     If the command continues to run after the wait period, the CLI returns control of the terminal window to you.
@@ -2968,201 +6873,346 @@ ENVIRONMENT VARIABLES
   SF_USE_PROGRESS_BAR  Set to false to disable the progress bar when running the metadata deploy command.
 ```
 
-## `sf retrieve metadata preview`
+_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/1.18.3/src/commands/project/retrieve/start.ts)_
 
-Preview a retrieval to see what will be retrieved from the org, the potential conflicts, and the ignored files.
+## `sf schema generate field`
+
+Generate metadata source files for a new custom field on a specified object.
 
 ```
 USAGE
-  $ sf retrieve metadata preview [--json] [-c] [-o <value>]
+  $ sf schema generate field -l <value> [-o <value>]
 
 FLAGS
-  -c, --ignore-conflicts    Ignore conflicts and preview the retrieve of remote components, even if they will overwrite
-                            local changes.
-  -o, --target-org=<value>  Login username or alias for the target org.
-
-GLOBAL FLAGS
-  --json  Format output as json.
+  -l, --label=<value>   (required) The field's label.
+  -o, --object=<value>  The directory that contains the object's source files.
 
 DESCRIPTION
-  Preview a retrieval to see what will be retrieved from the org, the potential conflicts, and the ignored files.
+  Generate metadata source files for a new custom field on a specified object.
 
-  You must run this command from within a project.
+  This command is interactive and must be run in a Salesforce DX project directory. You're required to specify the
+  field's label with the "--label" flag. The command uses this label to provide intelligent suggestions for other field
+  properties, such as its API name.
 
-  The command outputs a table that describes what will happen if you run the "sf retrieve metadata" command. The table
-  lists the metadata components that will be retrieved and deleted. The table also lists the current conflicts between
-  files in your local project and components in the org. Finally, the table lists the files that won't be retrieved
-  because they're included in your .forceignore file.
+  You can generate a custom field on either a standard object, such as Account, or a custom object. In both cases, the
+  source files for the object must already exist in your local project before you run this command. If you create a
+  relationship field, the source files for the parent object must also exist in your local directory.  Use the command
+  "sf metadata retrieve -m CustomObject:<object>" to retrieve source files for both standard and custom objects from
+  your org.  To create a custom object, run the "sf generate metadata sobject" command or use the Object Manager UI in
+  your Salesforce org.
 
-  If your org allows source tracking, then this command considers conflicts between the org and local. Some orgs, such
-  as production orgs, never allow source tracking. Use the "--no-track-source" flag when you create a scratch or sandbox
-  org to disable source tracking.
+ALIASES
+  $ sf generate metadata field
 
 EXAMPLES
-  Preview the retrieve of all changes from the org:
+  Create a field with the specified label; the command prompts you for the object:
 
-    $ sf retrieve metadata preview
+    $ sf schema generate field --label "My Field"
 
-  Preview the retrieve when ignoring any conflicts:
+  Specify the local path to the object's folder:
 
-    $ sf retrieve metadata preview --ignore-conflicts
+    $ sf schema generate field --label "My Field" --object force-app/main/default/objects/MyObject__c
 
 FLAG DESCRIPTIONS
-  -c, --ignore-conflicts
+  -o, --object=<value>  The directory that contains the object's source files.
 
-    Ignore conflicts and preview the retrieve of remote components, even if they will overwrite local changes.
+    The object source files in your local project are grouped in a directoy with the same name as the object. Custom
+    object names always end in "__c". An example of the object directory for the Account standard object is
+    "force-app/main/default/objects/Account" An example custom object directory is
+    "force-app/main/default/objects/MyObject__c"
 
-    This flag applies only to orgs that allow source tracking. It has no effect on orgs that don't allow it, such as
-    production orgs.
+    If you don't specify this flag, the command prompts you to choose from your local objects.
+```
 
-  -o, --target-org=<value>  Login username or alias for the target org.
+_See code: [@salesforce/plugin-sobject](https://github.com/salesforcecli/plugin-sobject/blob/0.2.8/src/commands/schema/generate/field.ts)_
 
-    Overrides your default org.
+## `sf schema generate platformevent`
+
+Generate metadata source files for a new platform event.
+
+```
+USAGE
+  $ sf schema generate platformevent -l <value>
+
+FLAGS
+  -l, --label=<value>  (required) The platform event's label.
+
+DESCRIPTION
+  Generate metadata source files for a new platform event.
+
+  This command is interactive and must be run in a Salesforce DX project directory. You're required to specify the
+  event's label with the "--label" flag. The command uses this label to provide intelligent suggestions for other event
+  properties, such as its API name.
+
+ALIASES
+  $ sf generate metadata platformevent
+
+EXAMPLES
+  Create a platform event with the specified label:
+
+    $ sf schema generate platformevent --label "My Platform Event"
 ```
 
-## `sf run function`
+_See code: [@salesforce/plugin-sobject](https://github.com/salesforcecli/plugin-sobject/blob/0.2.8/src/commands/schema/generate/platformevent.ts)_
+
+## `sf schema generate sobject`
 
-Send a cloudevent to a function.
+Generate metadata source files for a new custom object.
 
 ```
 USAGE
-  $ sf run function [--json] [-l <value> | ] [-H <value>] [-p <value>] [-s] [-o <value>]
+  $ sf schema generate sobject -l <value> [-f]
 
 FLAGS
-  -H, --headers=<value>...     Set headers.
-  -l, --function-url=<value>   URL of the function to run.
-  -o, --connected-org=<value>  Username or alias for the target org; overrides default target org.
-  -p, --payload=<value>        Set the payload of the cloudevent as a JSON object or a path to a file via @file.json.
-  -s, --structured             Set the cloudevent to be emitted as a structured JSON cloudevent.
+  -f, --use-default-features  Enable all optional features without prompting.
+  -l, --label=<value>         (required) The custom object's label.
 
-GLOBAL FLAGS
-  --json  Format output as json.
+DESCRIPTION
+  Generate metadata source files for a new custom object.
+
+  This command is interactive and must be run in a Salesforce DX project directory. You're required to specify the
+  object's label with the "--label" flag. The command uses this label to provide intelligent suggestions for other
+  object properties, such as its API name and plural label.
+
+  All Salesforce objects are required to have a Name field, so this command also prompts you for the label and type of
+  the Name field. Run the "sf metadata generate field" command to create additional fields for the object.
+
+  To reduce the number of prompts, use the "--use-default-features" flag to automatically enable some features, such as
+  reporting and search on the object.
+
+ALIASES
+  $ sf generate metadata sobject
 
 EXAMPLES
-  Run a function:
+  Create a custom object with the specified label and be prompted for additional information:
+
+    $ sf schema generate sobject --label "My Object"
+
+  Create a custom object and enable optional features without prompting:
+
+    $ sf schema generate sobject --label "My Object" --use-default-features
 
-    $ sf run function --url http://path/to/function
+FLAG DESCRIPTIONS
+  -f, --use-default-features  Enable all optional features without prompting.
 
-  Run a function with a payload and a JSON response:
+    Enables these features:
 
-    $ sf run function --url http://path/to/function --payload '@file.json' --structured
+    * Search: Allows users to find the custom object's records when they search, including SOSL.
+    * Feeds: Enables feed tracking.
+    * Reports: Allows reporting of the data in the custom object records.
+    * History: Enables object history tracking.
+    * Activities: Allows users to associate tasks and scheduled calendar events related to the custom object records.
+    * Bulk API: With Sharing and Streaming API, classifies the custom object as an Enterprise Application object.
+    * Sharing: With Bulk API and Streaming API, classifies the custom object as an Enterprise Application object.
+    * Streaming API: With Bulk API and Sharing, classifies the custom object as an Enterprise Application object.
 ```
 
-## `sf run function start`
+_See code: [@salesforce/plugin-sobject](https://github.com/salesforcecli/plugin-sobject/blob/0.2.8/src/commands/schema/generate/sobject.ts)_
+
+## `sf schema generate tab`
 
-Build and run a Salesforce Function.
+Generate the metadata source files for a new custom tab on a custom object.
 
 ```
 USAGE
-  $ sf run function start [-b <value>] [-l javascript|typescript|java|auto] [-p <value>] [-v]
+  $ sf schema generate tab -o <value> -d <value> -i <value> [--json]
 
 FLAGS
-  -b, --debug-port=<value>                          [default: 9229] Port for remote debugging.
-  -l, --language=(javascript|typescript|java|auto)  [default: auto] The language that the function runs in.
-  -p, --port=<value>                                [default: 8080] Port for running the function.
-  -v, --verbose                                     Output additional logs.
+  -d, --directory=<value>  (required) Path to a "tabs" directory that will contain the source files for your new tab.
+  -i, --icon=<value>       (required) [default: 1] Number from 1 to 100 that specifies the color scheme and icon for the
+                           custom tab.
+  -o, --object=<value>     (required) API name of the custom object you're generating a tab for.
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Build and run a Salesforce Function.
+  Generate the metadata source files for a new custom tab on a custom object.
 
-  Run this command from the directory of your Salesforce Functions project.
+  Custom tabs let you display custom object data or other web content in Salesforce. Custom tabs appear in Salesforce as
+  an item in the app’s navigation bar and in the App Launcher.
 
-  This command will run the target function locally (on the same operating system as this CLI), just like the `local`
-  subcommand.
+  This command must be run in a Salesforce DX project directory. You must pass all required information to it with the
+  required flags. The source files for the custom object for which you're generating a tab don't need to exist in your
+  local project.
 
-  Previously, this command ran functions in a container. Container mode is still supported via the `container`
-  subcommand. Arguments relevant to container mode are still accepted, but are deprecated, ignored, and will be dropped
-  in a future release.
+ALIASES
+  $ sf generate metadata tab
 
 EXAMPLES
-  Build a function and start the invoker
+  Create a tab on the MyObject__c custom object:
+
+    $ sf schema generate tab --object MyObject__c --icon 54 --directory force-app/main/default/tabs
+
+FLAG DESCRIPTIONS
+  -i, --icon=<value>  Number from 1 to 100 that specifies the color scheme and icon for the custom tab.
+
+    See https://lightningdesignsystem.com/icons/\#custom for the available icons.
 
-    $ sf run function start
+  -o, --object=<value>  API name of the custom object you're generating a tab for.
+
+    The API name for a custom object always ends in "__c", such as "MyObject__c".
+```
+
+_See code: [@salesforce/plugin-sobject](https://github.com/salesforcecli/plugin-sobject/blob/0.2.8/src/commands/schema/generate/tab.ts)_
+
+## `sf search`
+
+Search for a command.
+
+```
+USAGE
+  $ sf search
 
-  Start the invoker with a specific language and port
+DESCRIPTION
+  Search for a command.
 
-    $ sf run function start --port 5000 --language javascript
+  Once you select a command, hit enter and it will show the help for that command.
 ```
 
-## `sf run function start container`
+_See code: [@oclif/plugin-search](https://github.com/oclif/plugin-search/blob/0.0.23/dist/commands/search.ts)_
 
-Build and run a Salesforce Function in a container.
+## `sf sobject describe`
+
+Display the metadata for a standard or custom object or a Tooling API object.
 
 ```
 USAGE
-  $ sf run function start container [-p <value>] [-b <value>] [--clear-cache] [--no-pull] [-e <value>] [--network
-  <value>] [-v]
+  $ sf sobject describe -o <value> -s <value> [--json] [--api-version <value>] [-t]
 
 FLAGS
-  -b, --debug-port=<value>  [default: 9229] Port for remote debugging.
-  -e, --env=<value>...      Set environment variables (provided during build and run).
-  -p, --port=<value>        [default: 8080] Port for running the function.
-  -v, --verbose             Output additional logs.
-  --clear-cache             Clear associated cache before executing.
-  --network=<value>         Connect and build containers to a network. This can be useful to build containers which
-                            require a local resource.
-  --no-pull                 Skip pulling builder image before use.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     (required) API name of the object to describe.
+  -t, --use-tooling-api     Use Tooling API to display metadata for Tooling API objects.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Build and run a Salesforce Function in a container.
+  Display the metadata for a standard or custom object or a Tooling API object.
 
-  Run this command from the directory of your Salesforce Functions project.
+  The metadata is displayed in JSON format. See this topic for a description of each property: https://developer.salesfo
+  rce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_describesobjects_describesobjectresult.htm.
+
+  This command displays metadata for Salesforce objects by default. Use the --use-tooling-api flag to view metadata for
+  a Tooling API object.
+
+ALIASES
+  $ sf force schema sobject describe
 
 EXAMPLES
-  Build and run a function:
+  Display the metadata of the "Account" standard object in your default org:
 
-    $ sf run function start container
+    $ sf sobject describe --sobject Account
 
-  Run a function on a specific port with additional logs:
+  Display the metadata of the "MyObject__c" custom object in the org with alias "my-scratch-org":
 
-    $ sf run function start container --port 5000 --verbose
+    $ sf sobject describe --sobject MyObject__c --target-org my-scratch-org
 
-  Add environment variables and specify a network:
+  Display the metadata of the ApexCodeCoverage Tooling API object in your default org:
 
-    $ sf run function start container --env KEY=VALUE --network host
+    $ sf sobject describe --sobject ApexCodeCoverage --use-tooling-api
 ```
 
-## `sf run function start local`
+_See code: [@salesforce/plugin-schema](https://github.com/salesforcecli/plugin-schema/blob/2.3.29/src/commands/sobject/describe.ts)_
+
+## `sf sobject list`
 
-Build and run a Salesforce Function locally.
+List all Salesforce objects of a specified category.
 
 ```
 USAGE
-  $ sf run function start local [-p <value>] [-b <value>] [-l javascript|typescript|java|auto]
+  $ sf sobject list -o <value> [--json] [--api-version <value>] [-s <value>]
 
 FLAGS
-  -b, --debug-port=<value>                          [default: 9229] Port to use for debbugging the function.
-  -l, --language=(javascript|typescript|java|auto)  [default: auto] The language that the function runs in.
-  -p, --port=<value>                                [default: 8080] Port to bind the invoker to.
+  -o, --target-org=<value>  (required) Username or alias of the target org.
+  -s, --sobject=<value>     [default: ALL] Category of objects to list.
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Build and run a Salesforce Function locally.
+  List all Salesforce objects of a specified category.
+
+  You can list the standard objects, custom objects, or all. The lists include only Salesforce objects, not Tooling API
+  objects.
+
+ALIASES
+  $ sf force schema sobject list
 
 EXAMPLES
-  Build a function and start the invoker
+  List all objects in your default org:
 
-    $ sf run function start local
+    $ sf sobject list --sobject all
 
-  Start the invoker with a specific language and port
+  List only custom objects in the org with alias "my-scratch-org":
 
-    $ sf run function start local --port 5000 --language javascript
+    $ sf sobject list --sobject custom --target-org my-scratch-org
 ```
 
-## `sf search`
+_See code: [@salesforce/plugin-schema](https://github.com/salesforcecli/plugin-schema/blob/2.3.29/src/commands/sobject/list.ts)_
 
-Search for a command.
+## `sf static-resource generate`
+
+Generate a static resource.
 
 ```
 USAGE
-  $ sf search
+  $ sf static-resource generate -n <value> [--json] [--type <value>] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -n, --name=<value>        (required) Name of the generated static resource.
+  --api-version=<value>     Override the api version used for api requests made by this command
+  --type=<value>            [default: application/zip] Content type (mime type) of the generated static resource.
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Search for a command.
+  Generate a static resource.
 
-  Once you select a command, hit enter and it will show the help for that command.
+  Generates the metadata resource file in the specified directory or the current working directory. Static resource
+  files must be contained in a parent directory called "staticresources" in your package directory. Either run this
+  command from an existing directory of this name, or use the --output-dir flag to create one or point to an existing
+  one.
+
+ALIASES
+  $ sf force staticresource create
+
+EXAMPLES
+  Generate the metadata file for a static resource called MyResource in the current directory:
+
+    $ sf static-resource generate --name MyResource
+
+  Similar to previous example, but specifies a MIME type of application/json:
+
+    $ sf static-resource generate --name MyResource --type application/json
+
+  Generate the resource file in the "force-app/main/default/staticresources" directory:
+
+    $ sf static-resource generate --name MyResource --output-dir force-app/main/default/staticresources
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated static resource.
+
+    This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin
+    with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
+
+  --type=<value>  Content type (mime type) of the generated static resource.
+
+    Must be a valid MIME type such as application/json, application/javascript, application/zip, text/plain, text/css,
+    etc.
 ```
 
-_See code: [@oclif/plugin-search](https://github.com/oclif/plugin-search/blob/v0.0.1/dist/commands/search.ts)_
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/static-resource/generate.ts)_
 
 ## `sf update [CHANNEL]`
 
@@ -3199,7 +7249,7 @@ EXAMPLES
     $ sf update --available
 ```
 
-_See code: [@oclif/plugin-update](https://github.com/oclif/plugin-update/blob/v3.0.0/src/commands/update.ts)_
+_See code: [@oclif/plugin-update](https://github.com/oclif/plugin-update/blob/3.2.4/src/commands/update.ts)_
 
 ## `sf version`
 
@@ -3219,68 +7269,128 @@ FLAG DESCRIPTIONS
     Additionally shows the architecture, node version, operating system, and versions of plugins that the CLI is using.
 ```
 
-_See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/v1.1.2/src/commands/version.ts)_
+_See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/1.3.10/src/commands/version.ts)_
 
-## `sf whatsnew [-v <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`
+## `sf visualforce generate component`
 
-Display Salesforce CLI release notes on the command line.
+Generate a Visualforce Component.
 
 ```
 USAGE
-  $ sf whatsnew [-v <string>] [--json] [--loglevel
-    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf visualforce generate component -n <value> -l <value> [--json] [-t DefaultVFComponent] [-d <value>] [--api-version
+  <value>]
 
 FLAGS
-  -v, --version=<value>                                                             CLI version or tag for which to
-                                                                                    display release notes.
-  --json                                                                            format output as json
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -l, --label=<value>       (required) Visualforce Component label.
+  -n, --name=<value>        (required) Name of the generated Visualforce Component.
+  -t, --template=<option>   [default: DefaultVFComponent] Template to use for file creation.
+                            <options: DefaultVFComponent>
+  --api-version=<value>     Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Display Salesforce CLI release notes on the command line.
+  Generate a Visualforce Component.
+
+  The command generates the .Component file and associated metadata file in the specified directory or the current
+  working directory by default.
 
 ALIASES
-  $ sf whatsnew
+  $ sf force visualforce component create
 
 EXAMPLES
-  Display release notes for the currently installed CLI version:
+  Generate the metadata files for a Visualforce component in the current directory:
 
-  $ sf whatsnew
+    $ sf visualforce generate component --name mycomponent --label mylabel
 
-  Display release notes for CLI version 7.120.0:
+  Similar to previous example, but generate the files in the directory "force-app/main/default/components":
 
-  $ sf whatsnew --version 7.120.0
+    $ sf visualforce generate component --name mycomponent --label mylabel --output-dir components
 
-  Display release notes for the CLI version that corresponds to a tag (stable, stable-rc, latest, latest-rc, rc):
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Visualforce Component.
+
+    The name can be up to 40 characters and must start with a letter.
 
-  $ sf whatsnew --version latest
+  -t, --template=DefaultVFComponent  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-## `sf whoami functions`
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/visualforce/generate/component.ts)_
+
+## `sf visualforce generate page`
 
-Show information on your Salesforce Functions login.
+Generate a Visualforce Page.
 
 ```
 USAGE
-  $ sf whoami functions [--json]
+  $ sf visualforce generate page -n <value> -l <value> [--json] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>  [default: .] Directory for saving the created files.
+  -l, --label=<value>       (required) Visualforce Page label.
+  -n, --name=<value>        (required) Name of the generated Visualforce Page.
+  --api-version=<value>     Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Show information on your Salesforce Functions login.
+  Generate a Visualforce Page.
 
-  Returns your email and ID. Use '--show-token' to show your Salesforce Functions token.
+  The command generates the .Page file and associated metadata file in the specified directory or the current working
+  directory by default.
+
+ALIASES
+  $ sf force visualforce page create
 
 EXAMPLES
-  Get account information:
+  Generate the metadata files for a Visualforce page in the current directory:
+
+    $ sf visualforce generate page --name mypage --label mylabel
+
+  Similar to previous example, but generate the files in the directory "force-app/main/default/pages":
 
-    $ sf whoami functions
+    $ sf visualforce generate page --name mypage --label mylabel --output-dir pages
 
-  Show token and output result as JSON:
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Visualforce Page.
+
+    The name can be up to 40 characters and must start with a letter.
+```
+
+_See code: [@salesforce/plugin-templates](https://github.com/salesforcecli/plugin-templates/blob/55.5.14/src/commands/visualforce/generate/page.ts)_
+
+## `sf which`
+
+Show which plugin a command is in.
 
-    $ sf whoami functions --show-token --json
 ```
+USAGE
+  $ sf which
+
+DESCRIPTION
+  Show which plugin a command is in.
+
+EXAMPLES
+  See which plugin the `help` command is in:
+
+    $ sf which help
+```
+
+_See code: [@oclif/plugin-which](https://github.com/oclif/plugin-which/blob/2.2.33/src/commands/which.ts)_
 
 <!-- commandsstop -->
diff --git a/package.json b/package.json
index 8cfb59e1..7a32bd4e 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.12.1",
+  "version": "2.12.2",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run",
@@ -76,7 +76,7 @@
       "@salesforce/plugin-devops-center": "1.2.1",
       "@salesforce/plugin-env": "2.2.3",
       "@salesforce/plugin-functions": "1.22.3",
-      "@salesforce/plugin-packaging": "1.26.2",
+      "@salesforce/plugin-packaging": "1.26.3",
       "@salesforce/plugin-signups": "1.5.1",
       "@salesforce/sfdx-plugin-lwc-test": "1.1.0",
       "@salesforce/sfdx-scanner": "3.16.0"
@@ -188,8 +188,8 @@
   "resolutions": {
     "@salesforce/schemas": "1.6.0",
     "@salesforce/templates": "59.0.1",
-    "@salesforce/source-deploy-retrieve": "9.7.18",
-    "@salesforce/source-tracking": "4.2.14"
+    "@salesforce/source-deploy-retrieve": "9.7.19",
+    "@salesforce/source-tracking": "4.2.15"
   },
   "repository": "salesforcecli/cli",
   "scripts": {
diff --git a/yarn.lock b/yarn.lock
index 1eb249b6..8076327a 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -1681,10 +1681,10 @@
     strip-ansi "6.0.1"
     ts-retry-promise "^0.7.1"
 
-"@salesforce/core@^5.2.0", "@salesforce/core@^5.2.10", "@salesforce/core@^5.2.6", "@salesforce/core@^5.2.7", "@salesforce/core@^5.2.9":
-  version "5.2.10"
-  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-5.2.10.tgz#7f4824ddcef108b6ccec24434260c620de39012e"
-  integrity sha512-Xj1QRajmHWgl0ahivjKFGKJlGXwe9yFOZ3PwF91qEupGbO74XrCJ8OUM7EVlk53LKy9LlPZQFuy2ATX9MyEDKA==
+"@salesforce/core@^5.2.0", "@salesforce/core@^5.2.10", "@salesforce/core@^5.2.6", "@salesforce/core@^5.2.7", "@salesforce/core@^5.2.9", "@salesforce/core@^5.3.1":
+  version "5.3.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-5.3.1.tgz#93c49760faa7b503bbfea8376d80a66815065e4a"
+  integrity sha512-LEQ3Yp7GxexsGXxT85Pp4AgOzzqY9Y3kol8ByVsHpHGvs8XLRbKl44IPxTXBdMB2roFM+Iosd46i0KbTuh2MQg==
   dependencies:
     "@salesforce/kit" "^3.0.11"
     "@salesforce/schemas" "^1.6.0"
@@ -1754,10 +1754,10 @@
     typedoc-plugin-missing-exports "0.23.0"
     typescript "^4.1.3"
 
-"@salesforce/kit@^3.0.11", "@salesforce/kit@^3.0.9":
-  version "3.0.11"
-  resolved "https://registry.yarnpkg.com/@salesforce/kit/-/kit-3.0.11.tgz#d03160b658da9817c05e62479ca18283087a0fc0"
-  integrity sha512-ar44uFJfc/RCDWjz7LlrOtFCFHgNNUpddxe0eJCLqQuR/Xs3IlLZKuovWTx322Rzu+V9IIKrIdpz2IqA95/ClA==
+"@salesforce/kit@^3.0.11", "@salesforce/kit@^3.0.12", "@salesforce/kit@^3.0.9":
+  version "3.0.12"
+  resolved "https://registry.yarnpkg.com/@salesforce/kit/-/kit-3.0.12.tgz#8d598813fd3dce9545951186cfa579bafaac374a"
+  integrity sha512-+2bjUaIbS1/XrYBYxpS5zKyQER8dgVakIL6X/MxZVZFJaLHithkLXvrUKYd5tZEaijxBZq1ooIkGm2yCLrg8Ew==
   dependencies:
     "@salesforce/ts-types" "^2.0.7"
     tslib "^2.6.2"
@@ -2064,10 +2064,10 @@
     chalk "^4"
     inquirer "^8.2.5"
 
-"@salesforce/source-deploy-retrieve@9.7.18", "@salesforce/source-deploy-retrieve@^9.7.13", "@salesforce/source-deploy-retrieve@^9.7.15", "@salesforce/source-deploy-retrieve@^9.7.4":
-  version "9.7.18"
-  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-9.7.18.tgz#38b1577eec7ae08c3ed627c7a38f59c87632b01d"
-  integrity sha512-kdnX8P/cjUwgKnDF60kXlvm4zwP2xXpFqEB3KniSrvuvbzXKrPbaa05cJvHVnTohAcYTNPHiM+LNkTgZuENNmA==
+"@salesforce/source-deploy-retrieve@9.7.19", "@salesforce/source-deploy-retrieve@^9.7.13", "@salesforce/source-deploy-retrieve@^9.7.15", "@salesforce/source-deploy-retrieve@^9.7.18", "@salesforce/source-deploy-retrieve@^9.7.4":
+  version "9.7.19"
+  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-9.7.19.tgz#6550e4bc508584212d697c79537c75dabbb26cf1"
+  integrity sha512-DmQT/f53NjghZPmkWf6itJJ0AEto26KI3PFgxBbuA0/tK/xhlM/6U75DzBqrSWxWC7qKrOgdsdVgEkvvJR8HNg==
   dependencies:
     "@salesforce/core" "^5.2.10"
     "@salesforce/kit" "^3.0.11"
@@ -2083,15 +2083,15 @@
     proxy-agent "^6.3.1"
     unzipper "0.10.14"
 
-"@salesforce/source-tracking@4.2.14", "@salesforce/source-tracking@^4.2.10", "@salesforce/source-tracking@^4.2.12":
-  version "4.2.14"
-  resolved "https://registry.yarnpkg.com/@salesforce/source-tracking/-/source-tracking-4.2.14.tgz#27772df901efc81aa1f1c0a9f08d427d5c25b2ef"
-  integrity sha512-Oa9StBkvNlA5ER+n6hbgmQY991c6Pv0ms8SLMKh9s4EIA8lfZfqzSCNXOskMdO4zPnoJKPRfZNG0119krfbuhQ==
+"@salesforce/source-tracking@4.2.15", "@salesforce/source-tracking@^4.2.10", "@salesforce/source-tracking@^4.2.12":
+  version "4.2.15"
+  resolved "https://registry.yarnpkg.com/@salesforce/source-tracking/-/source-tracking-4.2.15.tgz#611043d5ceef2b8c3ecbe7ab51a5b84329a2c602"
+  integrity sha512-CfwtqaUUo3QQ0tbaJVzAxRMz3bMZkg2x0k9jyc9H8gjDM5O9z9GocTL7ZMLaYd2ahOiI+jAK86z1l3PS8wK/iA==
   dependencies:
-    "@salesforce/core" "^5.2.0"
-    "@salesforce/kit" "^3.0.9"
-    "@salesforce/source-deploy-retrieve" "^9.7.15"
-    "@salesforce/ts-types" "^2.0.6"
+    "@salesforce/core" "^5.3.1"
+    "@salesforce/kit" "^3.0.12"
+    "@salesforce/source-deploy-retrieve" "^9.7.18"
+    "@salesforce/ts-types" "^2.0.8"
     fast-xml-parser "^4.2.5"
     graceful-fs "^4.2.11"
     isomorphic-git "1.23.0"
@@ -2132,10 +2132,10 @@
     sinon "^5.1.1"
     tslib "^2.6.1"
 
-"@salesforce/ts-types@^2.0.6", "@salesforce/ts-types@^2.0.7":
-  version "2.0.7"
-  resolved "https://registry.yarnpkg.com/@salesforce/ts-types/-/ts-types-2.0.7.tgz#02a6999d0b0e7bcd6c6d8ce621c79fa61af24701"
-  integrity sha512-8csXgstPuy6QXL3JavkIi/f8DOWHBNCvWeszrFu5sbVlcKO3YqOOCE+rDFGPkrZsYv5OywV6H8kEi877bWOz6Q==
+"@salesforce/ts-types@^2.0.6", "@salesforce/ts-types@^2.0.7", "@salesforce/ts-types@^2.0.8":
+  version "2.0.8"
+  resolved "https://registry.yarnpkg.com/@salesforce/ts-types/-/ts-types-2.0.8.tgz#e732b5a42cbec6bda79c089a0633fc643daf8bca"
+  integrity sha512-vuzLcxtThBhpuhmnoh8GFrVU8XjdoNyQm9gPtmcjUyUD/9nQIBTAX8oGoUvCiiq93c4LFEmSua+xm3yu0bbNfg==
   dependencies:
     tslib "^2.6.2"