@salesforce/plugin-deploy-retrieve 1.3.0 → 1.4.0

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [1.4.0](https://github.com/salesforcecli/plugin-deploy-retrieve/compare/v1.3.0...v1.4.0) (2022-05-03)
+
+### Features
+
+- support all deploy workflows ([#234](https://github.com/salesforcecli/plugin-deploy-retrieve/issues/234)) ([29904cb](https://github.com/salesforcecli/plugin-deploy-retrieve/commit/29904cb5956433ed6fdde95a1d131d6539beeaa7)), closes [#235](https://github.com/salesforcecli/plugin-deploy-retrieve/issues/235) [#238](https://github.com/salesforcecli/plugin-deploy-retrieve/issues/238) [#239](https://github.com/salesforcecli/plugin-deploy-retrieve/issues/239) [#243](https://github.com/salesforcecli/plugin-deploy-retrieve/issues/243) [#244](https://github.com/salesforcecli/plugin-deploy-retrieve/issues/244)
+
 ## [1.3.0](https://github.com/salesforcecli/plugin-deploy-retrieve/compare/v1.2.1...v1.3.0) (2022-04-13)
 
 ### Features

package/README.md

@@ -64,6 +64,11 @@ sf plugins
 
 - [`sf deploy`](#sf-deploy)
 - [`sf deploy metadata`](#sf-deploy-metadata)
+- [`sf deploy metadata cancel`](#sf-deploy-metadata-cancel)
+- [`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 retrieve metadata`](#sf-retrieve-metadata)
 
 ## `sf deploy`
@@ -108,7 +113,7 @@ EXAMPLES
     $ sf deploy --interactive
 ```
 
-_See code: [src/commands/deploy.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/v1.2.1/src/commands/deploy.ts)_
+_See code: [src/commands/deploy.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/v1.3.0/src/commands/deploy.ts)_
 
 ## `sf deploy metadata`
 
@@ -116,8 +121,9 @@ Deploy metadata in source format to an org from your local project.
 
 ```
 USAGE
-  $ sf deploy metadata [--json] [-a <value>] [--dry-run] [-r] [-g] [-x <value>] [-m <value>] [-d <value>] [-o
-    <value>] [-t <value>] [-l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [--verbose] [-w <value>]
+  $ sf deploy metadata [--json] [-a <value>] [--async | -w <value>] [--concise | --verbose] [--dry-run] [-r] [-g] [-x
+    <value>] [-m <value>] [-d <value>] [-o <value>] [-t <value>] [-l
+    NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg]
 
 FLAGS
   -a, --api-version=<value>    Target API version for the deploy.
@@ -132,6 +138,8 @@ FLAGS
   -w, --wait=<minutes>         [default: 33 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.
   --verbose                    Show verbose output of the deploy result.
 
@@ -146,9 +154,6 @@ DESCRIPTION
   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.
 
-  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 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.
@@ -245,11 +250,384 @@ FLAG DESCRIPTIONS
 
   -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.
+    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".
 
   -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 deploy metadata resume". To check the status of the deployment, run "sf
+    deploy metadata report".
+```
+
+## `sf deploy metadata cancel`
+
+Cancel a deploy operation.
+
+```
+USAGE
+  $ sf deploy metadata 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.
+
+EXAMPLES
+  Cancel a deploy operation using a job ID:
+
+    $ sf deploy metadata cancel --job-id 0Af0x000017yLUFCA2
+
+  Cancel the most recent deploy operation:
+
+    $ sf deploy metadata 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 deploy metadata
+    - sf deploy metadata validate
+    - sf deploy metadata quick
+    - sf deploy metadata 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 deploy metadata resume". To check the status of the cancellation, run "sf
+    deploy metadata 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 deploy metadata resume". To check the status of the cancellation, run "sf
+    deploy metadata report".
+```
+
+## `sf deploy metadata quick`
+
+Quickly deploy a validated deployment to an org.
+
+```
+USAGE
+  $ sf deploy metadata quick [--json] [--async | -w <value>] [--concise | --verbose] [-i <value>] [-o <value>] [-r]
+
+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>      [default: 33 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.
+
+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.
+
+EXAMPLES
+  Run a quick deploy to your default org using a job ID:
+
+    $ sf deploy metadata quick --job-id 0Af0x000017yLUFCA2
+
+  Asynchronously run a quick deploy of the most recently validated deployment to an org with alias "my-prod-org":
+
+    $ sf deploy metadata quick --async --use-most-recent --target-org my-prod-org
+
+FLAG DESCRIPTIONS
+  -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 deploy metadata resume". To check the status of the deploy, run "sf deploy
+    metadata 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 deploy metadata resume". To check the status of the deploy, run "sf deploy
+    metadata report".
+```
+
+## `sf deploy metadata report`
+
+Check the status of a deploy operation.
+
+```
+USAGE
+  $ sf deploy metadata report [--json] [-i <value>] [-r]
+
+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.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Check 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.
+
+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:
+
+    - sf deploy metadata
+    - sf deploy metadata validate
+    - sf deploy metadata quick
+    - sf deploy metadata 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.
+```
+
+## `sf deploy metadata resume`
+
+Resume watching a deploy operation.
+
+```
+USAGE
+  $ sf deploy metadata resume [--json] [--concise | --verbose] [-i <value>] [-r] [-w <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.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Resume watching a deploy operation.
+
+  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.
+
+  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.
+
+EXAMPLES
+  Resume watching a deploy operation using a job ID:
+
+    $ sf deploy metadata resume --job-id 0Af0x000017yLUFCA2
+
+  Resume watching the most recent deploy operation:
+
+    $ sf deploy metadata 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 deploy metadata
+    - sf deploy metadata validate
+    - sf deploy metadata quick
+    - sf deploy metadata 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
+    deploy metadata report".
+```
+
+## `sf deploy metadata validate`
+
+Validate a metadata deployment without actually executing it.
+
+```
+USAGE
+  $ sf deploy metadata validate [--json] [-a <value>] [--async] [--concise | --verbose] [-x <value> | -m <value> | -d <value>]
+    [-o <value>] [-t <value>] [-l RunAllTestsInOrg|RunLocalTests|RunSpecifiedTests] [-w <value>]
+
+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>         [default: 33 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.
+  --verbose                    Show verbose output of the validation result.
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+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 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.
+
+  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.
+
+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.
+
+  Validate the deployment of all source files in a directory to the default org:
+
+    $ sf deploy metadata 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 deploy metadata 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 deploy metadata 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, which is the latest version supported the CLI, with the API
+    version in your package.xml file.
+
+  -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 --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".
 ```
 
 ## `sf retrieve metadata`

package/lib/commands/deploy/metadata/cancel.d.ts

@@ -0,0 +1,18 @@
+import { Duration } from '@salesforce/kit';
+import { SfCommand } from '@salesforce/sf-plugins-core';
+import { DeployResultJson } from '../../../utils/types';
+export default class DeployMetadataCancel extends SfCommand<DeployResultJson> {
+    static readonly description: string;
+    static readonly summary: string;
+    static readonly examples: string[];
+    static readonly requiresProject = true;
+    static readonly state = "beta";
+    static flags: {
+        async: import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        'job-id': import("@oclif/core/lib/interfaces").OptionFlag<string>;
+        'use-most-recent': import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        wait: import("@oclif/core/lib/interfaces").OptionFlag<Duration>;
+    };
+    run(): Promise<DeployResultJson>;
+    protected catch(error: SfCommand.Error): Promise<SfCommand.Error>;
+}

package/lib/commands/deploy/metadata/cancel.js

@@ -0,0 +1,86 @@
+"use strict";
+/*
+ * Copyright (c) 2022, salesforce.com, inc.
+ * All rights reserved.
+ * Licensed under the BSD 3-Clause license.
+ * For full license text, see LICENSE.txt file in the repo root or https://opensource.org/licenses/BSD-3-Clause
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+const core_1 = require("@salesforce/core");
+const kit_1 = require("@salesforce/kit");
+const sf_plugins_core_1 = require("@salesforce/sf-plugins-core");
+const deploy_1 = require("../../../utils/deploy");
+const output_1 = require("../../../utils/output");
+core_1.Messages.importMessagesDirectory(__dirname);
+const messages = core_1.Messages.loadMessages('@salesforce/plugin-deploy-retrieve', 'deploy.metadata.cancel');
+class DeployMetadataCancel extends sf_plugins_core_1.SfCommand {
+    async run() {
+        const { flags } = await this.parse(DeployMetadataCancel);
+        const cache = await deploy_1.DeployCache.create();
+        const jobId = cache.resolveLatest(flags['use-most-recent'], flags['job-id']);
+        const deployOpts = cache.get(jobId);
+        if (flags.async) {
+            const asyncResult = await (0, deploy_1.cancelDeployAsync)({ 'target-org': deployOpts['target-org'] }, jobId);
+            const formatter = new output_1.AsyncDeployCancelResultFormatter(asyncResult.id);
+            if (!this.jsonEnabled())
+                formatter.display();
+            return formatter.getJson();
+        }
+        else {
+            const wait = flags.wait || kit_1.Duration.minutes(deployOpts.wait);
+            const result = await (0, deploy_1.cancelDeploy)({ ...deployOpts, wait }, jobId);
+            const formatter = new output_1.DeployCancelResultFormatter(result);
+            if (!this.jsonEnabled())
+                formatter.display();
+            if ((0, deploy_1.shouldRemoveFromCache)(result.response.status)) {
+                cache.unset(result.response.id);
+                cache.unset(jobId);
+                await cache.write();
+            }
+            return formatter.getJson();
+        }
+    }
+    catch(error) {
+        if (error.name.includes('INVALID_ID_FIELD')) {
+            const err = messages.createError('error.CannotCancelDeploy');
+            return super.catch({ ...error, name: err.name, message: err.message, code: err.code });
+        }
+        return super.catch(error);
+    }
+}
+exports.default = DeployMetadataCancel;
+DeployMetadataCancel.description = messages.getMessage('description');
+DeployMetadataCancel.summary = messages.getMessage('summary');
+DeployMetadataCancel.examples = messages.getMessages('examples');
+DeployMetadataCancel.requiresProject = true;
+DeployMetadataCancel.state = 'beta';
+DeployMetadataCancel.flags = {
+    async: sf_plugins_core_1.Flags.boolean({
+        summary: messages.getMessage('flags.async.summary'),
+        description: messages.getMessage('flags.async.description'),
+        exclusive: ['wait'],
+    }),
+    'job-id': sf_plugins_core_1.Flags.salesforceId({
+        char: 'i',
+        startsWith: '0Af',
+        description: messages.getMessage('flags.job-id.description'),
+        summary: messages.getMessage('flags.job-id.summary'),
+        exactlyOne: ['use-most-recent', 'job-id'],
+    }),
+    'use-most-recent': sf_plugins_core_1.Flags.boolean({
+        char: 'r',
+        description: messages.getMessage('flags.use-most-recent.description'),
+        summary: messages.getMessage('flags.use-most-recent.summary'),
+        exactlyOne: ['use-most-recent', 'job-id'],
+    }),
+    wait: sf_plugins_core_1.Flags.duration({
+        char: 'w',
+        summary: messages.getMessage('flags.wait.summary'),
+        description: messages.getMessage('flags.wait.description'),
+        unit: 'minutes',
+        helpValue: '<minutes>',
+        min: 1,
+        exclusive: ['async'],
+    }),
+};
+//# sourceMappingURL=cancel.js.map

package/lib/commands/deploy/metadata/cancel.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cancel.js","sourceRoot":"","sources":["../../../../src/commands/deploy/metadata/cancel.ts"],"names":[],"mappings":";AAAA;;;;;GAKG;;AAEH,2CAA4C;AAC5C,yCAA2C;AAC3C,iEAA+D;AAC/D,kDAA4G;AAC5G,kDAAsG;AAGtG,eAAQ,CAAC,uBAAuB,CAAC,SAAS,CAAC,CAAC;AAC5C,MAAM,QAAQ,GAAG,eAAQ,CAAC,YAAY,CAAC,oCAAoC,EAAE,wBAAwB,CAAC,CAAC;AAEvG,MAAqB,oBAAqB,SAAQ,2BAA2B;IAqCpE,KAAK,CAAC,GAAG;QACd,MAAM,EAAE,KAAK,EAAE,GAAG,MAAM,IAAI,CAAC,KAAK,CAAC,oBAAoB,CAAC,CAAC;QACzD,MAAM,KAAK,GAAG,MAAM,oBAAW,CAAC,MAAM,EAAE,CAAC;QACzC,MAAM,KAAK,GAAG,KAAK,CAAC,aAAa,CAAC,KAAK,CAAC,iBAAiB,CAAC,EAAE,KAAK,CAAC,QAAQ,CAAC,CAAC,CAAC;QAE7E,MAAM,UAAU,GAAG,KAAK,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC;QAEpC,IAAI,KAAK,CAAC,KAAK,EAAE;YACf,MAAM,WAAW,GAAG,MAAM,IAAA,0BAAiB,EAAC,EAAE,YAAY,EAAE,UAAU,CAAC,YAAY,CAAC,EAAE,EAAE,KAAK,CAAC,CAAC;YAC/F,MAAM,SAAS,GAAG,IAAI,yCAAgC,CAAC,WAAW,CAAC,EAAE,CAAC,CAAC;YACvE,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE;gBAAE,SAAS,CAAC,OAAO,EAAE,CAAC;YAC7C,OAAO,SAAS,CAAC,OAAO,EAAE,CAAC;SAC5B;aAAM;YACL,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,IAAI,cAAQ,CAAC,OAAO,CAAC,UAAU,CAAC,IAAI,CAAC,CAAC;YAC7D,MAAM,MAAM,GAAG,MAAM,IAAA,qBAAY,EAAC,EAAE,GAAG,UAAU,EAAE,IAAI,EAAE,EAAE,KAAK,CAAC,CAAC;YAClE,MAAM,SAAS,GAAG,IAAI,oCAA2B,CAAC,MAAM,CAAC,CAAC;YAC1D,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE;gBAAE,SAAS,CAAC,OAAO,EAAE,CAAC;YAE7C,IAAI,IAAA,8BAAqB,EAAC,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE;gBACjD,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC;gBAChC,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC;gBACnB,MAAM,KAAK,CAAC,KAAK,EAAE,CAAC;aACrB;YACD,OAAO,SAAS,CAAC,OAAO,EAAE,CAAC;SAC5B;IACH,CAAC;IAES,KAAK,CAAC,KAAsB;QACpC,IAAI,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,kBAAkB,CAAC,EAAE;YAC3C,MAAM,GAAG,GAAG,QAAQ,CAAC,WAAW,CAAC,0BAA0B,CAAC,CAAC;YAC7D,OAAO,KAAK,CAAC,KAAK,CAAC,EAAE,GAAG,KAAK,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,OAAO,EAAE,GAAG,CAAC,OAAO,EAAE,IAAI,EAAE,GAAG,CAAC,IAAI,EAAE,CAAC,CAAC;SACxF;QACD,OAAO,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAC5B,CAAC;;AAtEH,uCAuEC;AAtEwB,gCAAW,GAAG,QAAQ,CAAC,UAAU,CAAC,aAAa,CAAC,CAAC;AACjD,4BAAO,GAAG,QAAQ,CAAC,UAAU,CAAC,SAAS,CAAC,CAAC;AACzC,6BAAQ,GAAG,QAAQ,CAAC,WAAW,CAAC,UAAU,CAAC,CAAC;AAC5C,oCAAe,GAAG,IAAI,CAAC;AACvB,0BAAK,GAAG,MAAM,CAAC;AAExB,0BAAK,GAAG;IACpB,KAAK,EAAE,uBAAK,CAAC,OAAO,CAAC;QACnB,OAAO,EAAE,QAAQ,CAAC,UAAU,CAAC,qBAAqB,CAAC;QACnD,WAAW,EAAE,QAAQ,CAAC,UAAU,CAAC,yBAAyB,CAAC;QAC3D,SAAS,EAAE,CAAC,MAAM,CAAC;KACpB,CAAC;IACF,QAAQ,EAAE,uBAAK,CAAC,YAAY,CAAC;QAC3B,IAAI,EAAE,GAAG;QACT,UAAU,EAAE,KAAK;QACjB,WAAW,EAAE,QAAQ,CAAC,UAAU,CAAC,0BAA0B,CAAC;QAC5D,OAAO,EAAE,QAAQ,CAAC,UAAU,CAAC,sBAAsB,CAAC;QACpD,UAAU,EAAE,CAAC,iBAAiB,EAAE,QAAQ,CAAC;KAC1C,CAAC;IACF,iBAAiB,EAAE,uBAAK,CAAC,OAAO,CAAC;QAC/B,IAAI,EAAE,GAAG;QACT,WAAW,EAAE,QAAQ,CAAC,UAAU,CAAC,mCAAmC,CAAC;QACrE,OAAO,EAAE,QAAQ,CAAC,UAAU,CAAC,+BAA+B,CAAC;QAC7D,UAAU,EAAE,CAAC,iBAAiB,EAAE,QAAQ,CAAC;KAC1C,CAAC;IACF,IAAI,EAAE,uBAAK,CAAC,QAAQ,CAAC;QACnB,IAAI,EAAE,GAAG;QACT,OAAO,EAAE,QAAQ,CAAC,UAAU,CAAC,oBAAoB,CAAC;QAClD,WAAW,EAAE,QAAQ,CAAC,UAAU,CAAC,wBAAwB,CAAC;QAC1D,IAAI,EAAE,SAAS;QACf,SAAS,EAAE,WAAW;QACtB,GAAG,EAAE,CAAC;QACN,SAAS,EAAE,CAAC,OAAO,CAAC;KACrB,CAAC;CACH,CAAC"}

package/lib/commands/deploy/metadata/quick.d.ts

@@ -0,0 +1,23 @@
+import { Org } from '@salesforce/core';
+import { SfCommand } from '@salesforce/sf-plugins-core';
+import { DeployResultJson } from '../../../utils/types';
+export default class DeployMetadataQuick extends SfCommand<DeployResultJson> {
+    static readonly description: string;
+    static readonly summary: string;
+    static readonly examples: string[];
+    static readonly requiresProject = true;
+    static readonly state = "beta";
+    static flags: {
+        async: import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        concise: import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        'job-id': import("@oclif/core/lib/interfaces").OptionFlag<string>;
+        'target-org': import("@oclif/core/lib/interfaces").OptionFlag<Org>;
+        'use-most-recent': import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        verbose: import("@oclif/core/lib/interfaces").BooleanFlag<boolean>;
+        wait: import("@oclif/core/lib/interfaces").OptionFlag<import("@salesforce/kit").Duration>;
+    };
+    static errorCodes: import("@salesforce/sf-plugins-core/lib/util").HelpSection;
+    run(): Promise<DeployResultJson>;
+    protected catch(error: SfCommand.Error): Promise<SfCommand.Error>;
+    private setExitCode;
+}