@salesforce/plugin-devops-center 1.0.0-beta.1 → 1.0.0-beta.2

package/messages/project.deploy.pipeline.quick.md

@@ -0,0 +1,45 @@
+# summary
+
+Quickly deploy a validated deployment to an org.
+
+# description
+
+Before you run this command, first create a validated deployment with the "sf project deploy pipeline 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 using your default Devops Center org and a job ID:
+
+      <%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2
+
+- Asynchronously run a quick deploy of the most recently validated deployment using an org with alias "my-prod-org":
+
+      <%= config.bin %> <%= command.id %> --async --use-most-recent --devops-center-username my-prod-org
+
+# flags.job-id.summary
+
+Job ID of the validated deployment to quick deploy.
+
+# flags.job-id.description
+
+The job ID is valid for 10 days from when you started the validation.
+
+# flags.use-most-recent.summary
+
+Use the job ID of the most recently validated deployment.
+
+# flags.use-most-recent.description
+
+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 the job ID.
+
+# error.JobIsNotValidationDeployment
+
+The job ID is invalid for the quick deployment. Verify that a deployment validation was run or hasn't expired, and that you specified the correct job ID. Then try again.
+
+# error.JobIsNotValidated
+
+We can't perform the quick deployment for the specified job ID because the validate-only deployment failed or is still running. If the validate-only deployment failed, fix the issue and re-run it. If the validate-only deployment was successful, try this command again later.

package/messages/project.deploy.pipeline.report.md

@@ -4,7 +4,7 @@ Check the status of a pipeline deploy operation.
 
 # description
 
-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.
+Run this command by either indicating a job ID or specifying the —use-most-recent flag to use the job ID of the most recent deploy operation.
 
 # examples
 
@@ -18,7 +18,7 @@ Run this command by either passing it a job ID or specifying the —use-most-rec
 
 # flags.job-id.summary
 
-Job ID of the pipeline deployment you want to check the status of.
+Job ID of the pipeline deployment to check the status of.
 
 # flags.job-id.description
 
@@ -30,7 +30,7 @@ Use the job ID of the most recent deploy operation.
 
 # flags.use-most-recent.description
 
-For performance reasons, this flag uses job IDs for deploy operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find a job ID.
+For performance reasons, this flag uses job IDs for deploy operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find the job ID.
 
 # report.key.created-by-name
 

package/messages/project.deploy.pipeline.resume.md

@@ -6,7 +6,7 @@ Resume watching a pipeline deploy operation.
 
 Use this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.
 
-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.
+Run this command by either indicating a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.
 
 # examples
 

package/messages/project.deploy.pipeline.start.md

@@ -4,7 +4,7 @@ Deploy changes from a branch to the pipeline stage’s org.
 
 # description
 
-Before you run this command, changes in the branch must be merged in the source control repository.
+Before you run this command, changes in the pipeline stage's branch must be merged in the source control repository.
 
 # examples
 
@@ -35,3 +35,7 @@ Path
 # deployComponent.table.title
 
 Deployed Source
+
+# deployComponent.table.validateDeployTitle
+
+Validate-only Deployed Source

package/messages/project.deploy.pipeline.validate.md

@@ -0,0 +1,17 @@
+# summary
+
+Perform a validate-only deployment from a branch to the pipeline stage’s org.
+
+# description
+
+A validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.
+
+# examples
+
+- Perform a validate-only deployment from the Staging branch to the Staging environment (sandbox):
+
+  <%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox
+
+- Perform a validate-only deployment of all changes from the main branch to the release environment:
+
+  <%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all

package/messages/promoteFlags.md

@@ -1,10 +1,10 @@
 # promote.branch-name.summary
 
-Name of the branch in the source control repository from which to deploy changes to the stage’s org.
+Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.
 
 # promote.deploy-all.summary
 
-Deploy all metadata in branch.
+Deploy all metadata in the branch to the stage's org.
 
 # promote.deploy-all.description
 
@@ -24,7 +24,7 @@ Apex tests to run when --test-level is RunSpecifiedTests.
 
 # promote.tests.description
 
-Separate multiple test names with commas, and enclose the entire flag value in double quotes if a test name contains a space.
+Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.
 
 # promote.test-level.summary
 

package/oclif.manifest.json

@@ -1,10 +1,98 @@
 {
-  "version": "1.0.0-beta.1",
+  "version": "1.0.0-beta.2",
   "commands": {
+    "project:deploy:pipeline:quick": {
+      "id": "project:deploy:pipeline:quick",
+      "summary": "Quickly deploy a validated deployment to an org.",
+      "description": "Before you run this command, first create a validated deployment with the \"sf project deploy pipeline 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.\n\nExecuting 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.\n\nThis 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.",
+      "strict": true,
+      "pluginName": "@salesforce/plugin-devops-center",
+      "pluginAlias": "@salesforce/plugin-devops-center",
+      "pluginType": "core",
+      "state": "beta",
+      "aliases": [],
+      "examples": [
+        "Run a quick deploy using your default Devops Center org and a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
+        "Asynchronously run a quick deploy of the most recently validated deployment using an org with alias \"my-prod-org\":\n<%= config.bin %> <%= command.id %> --async --use-most-recent --devops-center-username my-prod-org"
+      ],
+      "flags": {
+        "json": {
+          "name": "json",
+          "type": "boolean",
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "allowNo": false
+        },
+        "async": {
+          "name": "async",
+          "type": "boolean",
+          "summary": "Run the command asynchronously.",
+          "description": "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 pipeline resume\". To check the status of the deployment, run \"sf project deploy pipeline report\".",
+          "allowNo": false
+        },
+        "concise": {
+          "name": "concise",
+          "type": "boolean",
+          "summary": "Show concise output of the command result.",
+          "allowNo": false,
+          "exclusive": [
+            "verbose"
+          ]
+        },
+        "verbose": {
+          "name": "verbose",
+          "type": "boolean",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false
+        },
+        "wait": {
+          "name": "wait",
+          "type": "option",
+          "char": "w",
+          "summary": "Number of minutes to wait for command to complete and display results.",
+          "description": "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 check the status of the operation, run \"<%= config.bin %> <%= command.id.split(' ').slice(0, -1).join(' ') %> report\".",
+          "helpValue": "<minutes>",
+          "multiple": false,
+          "exclusive": [
+            "async"
+          ],
+          "default": {
+            "quantity": 33,
+            "unit": 0
+          }
+        },
+        "devops-center-username": {
+          "name": "devops-center-username",
+          "type": "option",
+          "char": "c",
+          "summary": "Username or alias of the DevOps Center org.",
+          "required": true,
+          "multiple": false
+        },
+        "job-id": {
+          "name": "job-id",
+          "type": "option",
+          "char": "i",
+          "summary": "Job ID of the validated deployment to quick deploy.",
+          "description": "The job ID is valid for 10 days from when you started the validation.",
+          "multiple": false
+        },
+        "use-most-recent": {
+          "name": "use-most-recent",
+          "type": "boolean",
+          "char": "r",
+          "summary": "Use the job ID of the most recently validated deployment.",
+          "description": "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 the job ID.",
+          "allowNo": false
+        }
+      },
+      "args": {},
+      "hasDynamicHelp": true
+    },
     "project:deploy:pipeline:report": {
       "id": "project:deploy:pipeline:report",
       "summary": "Check the status of a pipeline deploy operation.",
-      "description": "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.",
+      "description": "Run this command by either indicating a job ID or specifying the —use-most-recent flag to use the job ID of the most recent deploy operation.",
       "strict": true,
       "pluginName": "@salesforce/plugin-devops-center",
       "pluginAlias": "@salesforce/plugin-devops-center",
@@ -35,7 +123,7 @@
           "name": "job-id",
           "type": "option",
           "char": "i",
-          "summary": "Job ID of the pipeline deployment you want to check the status of.",
+          "summary": "Job ID of the pipeline deployment to check the status of.",
           "description": "The job ID is valid for 10 days from when you started the deploy operation.",
           "multiple": false
         },
@@ -44,7 +132,7 @@
           "type": "boolean",
           "char": "r",
           "summary": "Use the job ID of the most recent deploy operation.",
-          "description": "For performance reasons, this flag uses job IDs for deploy operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find a job ID.",
+          "description": "For performance reasons, this flag uses job IDs for deploy operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find the job ID.",
           "allowNo": false
         }
       },
@@ -54,7 +142,7 @@
     "project:deploy:pipeline:resume": {
       "id": "project:deploy:pipeline:resume",
       "summary": "Resume watching a pipeline deploy operation.",
-      "description": "Use this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.\n\nRun 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.",
+      "description": "Use this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.\n\nRun this command by either indicating a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
       "strict": true,
       "pluginName": "@salesforce/plugin-devops-center",
       "pluginAlias": "@salesforce/plugin-devops-center",
@@ -97,6 +185,21 @@
           "description": "For performance reasons, this flag uses job IDs for operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find a job ID.",
           "allowNo": false
         },
+        "concise": {
+          "name": "concise",
+          "type": "boolean",
+          "summary": "Show concise output of the command result.",
+          "allowNo": false,
+          "exclusive": [
+            "verbose"
+          ]
+        },
+        "verbose": {
+          "name": "verbose",
+          "type": "boolean",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false
+        },
         "wait": {
           "name": "wait",
           "type": "option",
@@ -120,7 +223,7 @@
     "project:deploy:pipeline:start": {
       "id": "project:deploy:pipeline:start",
       "summary": "Deploy changes from a branch to the pipeline stage’s org.",
-      "description": "Before you run this command, changes in the branch must be merged in the source control repository.",
+      "description": "Before you run this command, changes in the pipeline stage's branch must be merged in the source control repository.",
       "strict": true,
       "pluginName": "@salesforce/plugin-devops-center",
       "pluginAlias": "@salesforce/plugin-devops-center",
@@ -143,7 +246,133 @@
           "name": "branch-name",
           "type": "option",
           "char": "b",
-          "summary": "Name of the branch in the source control repository from which to deploy changes to the stage’s org.",
+          "summary": "Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.",
+          "required": true,
+          "multiple": false
+        },
+        "bundle-version-name": {
+          "name": "bundle-version-name",
+          "type": "option",
+          "char": "v",
+          "summary": "Version name of the bundle.",
+          "description": "You must indicate the bundle version if deploying to the environment that corresponds to the first stage after the bundling stage.",
+          "multiple": false
+        },
+        "deploy-all": {
+          "name": "deploy-all",
+          "type": "boolean",
+          "char": "a",
+          "summary": "Deploy all metadata in the branch to the stage's org.",
+          "description": "If you don’t specify this flag, only changes in the stage’s branch are deployed.",
+          "allowNo": false
+        },
+        "devops-center-project-name": {
+          "name": "devops-center-project-name",
+          "type": "option",
+          "char": "p",
+          "summary": "Name of the DevOps Center project.",
+          "required": true,
+          "multiple": false
+        },
+        "devops-center-username": {
+          "name": "devops-center-username",
+          "type": "option",
+          "char": "c",
+          "summary": "Username or alias of the DevOps Center org.",
+          "required": true,
+          "multiple": false
+        },
+        "tests": {
+          "name": "tests",
+          "type": "option",
+          "char": "t",
+          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
+          "description": "Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.",
+          "multiple": true
+        },
+        "test-level": {
+          "name": "test-level",
+          "type": "option",
+          "char": "l",
+          "summary": "Deployment Apex testing level.",
+          "description": "Valid values are:\n\n- 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.\n\n- 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.\n\n- 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.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\nIf 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\".",
+          "multiple": false,
+          "options": [
+            "NoTestRun",
+            "RunSpecifiedTests",
+            "RunLocalTests",
+            "RunAllTestsInOrg"
+          ]
+        },
+        "async": {
+          "name": "async",
+          "type": "boolean",
+          "summary": "Run the command asynchronously.",
+          "description": "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 pipeline resume\". To check the status of the deployment, run \"sf project deploy pipeline report\".",
+          "allowNo": false
+        },
+        "wait": {
+          "name": "wait",
+          "type": "option",
+          "char": "w",
+          "summary": "Number of minutes to wait for command to complete and display results.",
+          "description": "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 check the status of the operation, run \"<%= config.bin %> <%= command.id.split(' ').slice(0, -1).join(' ') %> report\".",
+          "helpValue": "<minutes>",
+          "multiple": false,
+          "exclusive": [
+            "async"
+          ],
+          "default": {
+            "quantity": 33,
+            "unit": 0
+          }
+        },
+        "verbose": {
+          "name": "verbose",
+          "type": "boolean",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false
+        },
+        "concise": {
+          "name": "concise",
+          "type": "boolean",
+          "summary": "Show concise output of the command result.",
+          "allowNo": false,
+          "exclusive": [
+            "verbose"
+          ]
+        }
+      },
+      "args": {},
+      "hasDynamicHelp": true
+    },
+    "project:deploy:pipeline:validate": {
+      "id": "project:deploy:pipeline:validate",
+      "summary": "Perform a validate-only deployment from a branch to the pipeline stage’s org.",
+      "description": "A validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.",
+      "strict": true,
+      "pluginName": "@salesforce/plugin-devops-center",
+      "pluginAlias": "@salesforce/plugin-devops-center",
+      "pluginType": "core",
+      "state": "beta",
+      "aliases": [],
+      "examples": [
+        "Perform a validate-only deployment from the Staging branch to the Staging environment (sandbox):\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox",
+        "Perform a validate-only deployment of all changes from the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
+      ],
+      "flags": {
+        "json": {
+          "name": "json",
+          "type": "boolean",
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "allowNo": false
+        },
+        "branch-name": {
+          "name": "branch-name",
+          "type": "option",
+          "char": "b",
+          "summary": "Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.",
           "required": true,
           "multiple": false
         },
@@ -159,7 +388,7 @@
           "name": "deploy-all",
           "type": "boolean",
           "char": "a",
-          "summary": "Deploy all metadata in branch.",
+          "summary": "Deploy all metadata in the branch to the stage's org.",
           "description": "If you don’t specify this flag, only changes in the stage’s branch are deployed.",
           "allowNo": false
         },
@@ -184,7 +413,7 @@
           "type": "option",
           "char": "t",
           "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
-          "description": "Separate multiple test names with commas, and enclose the entire flag value in double quotes if a test name contains a space.",
+          "description": "Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.",
           "multiple": true
         },
         "test-level": {