@salesforce/plugin-devops-center 1.2.9 → 1.2.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (47) hide show
  1. package/README.md +24 -10
  2. package/lib/commands/project/deploy/pipeline/quick.js +1 -1
  3. package/lib/commands/project/deploy/pipeline/quick.js.map +1 -1
  4. package/lib/commands/project/deploy/pipeline/report.js +1 -1
  5. package/lib/commands/project/deploy/pipeline/report.js.map +1 -1
  6. package/lib/commands/project/deploy/pipeline/resume.js +1 -1
  7. package/lib/commands/project/deploy/pipeline/resume.js.map +1 -1
  8. package/lib/commands/project/deploy/pipeline/start.js +1 -1
  9. package/lib/commands/project/deploy/pipeline/start.js.map +1 -1
  10. package/lib/commands/project/deploy/pipeline/validate.js +1 -1
  11. package/lib/commands/project/deploy/pipeline/validate.js.map +1 -1
  12. package/lib/common/base/abstractAsyncOperation.js.map +1 -1
  13. package/lib/common/base/abstractPromote.d.ts +5 -5
  14. package/lib/common/base/abstractPromote.js.map +1 -1
  15. package/lib/common/base/abstractQuick.d.ts +1 -1
  16. package/lib/common/base/abstractQuick.js +1 -1
  17. package/lib/common/base/abstractQuick.js.map +1 -1
  18. package/lib/common/base/abstractReportOnPromote.js.map +1 -1
  19. package/lib/common/base/abstractResume.d.ts +2 -2
  20. package/lib/common/base/abstractResume.js.map +1 -1
  21. package/lib/common/constants.js +1 -1
  22. package/lib/common/constants.js.map +1 -1
  23. package/lib/common/deployPipelineCache.js.map +1 -1
  24. package/lib/common/flags/flags.js +3 -0
  25. package/lib/common/flags/flags.js.map +1 -1
  26. package/lib/common/outputService/aorOutputService.js.map +1 -1
  27. package/lib/common/outputService/deploySummaryBuilder.js.map +1 -1
  28. package/lib/common/outputService/promoteOutputService.js.map +1 -1
  29. package/lib/common/outputService/resumeOutputService.js.map +1 -1
  30. package/lib/common/selectors/selectorUtils.js +1 -1
  31. package/lib/common/selectors/selectorUtils.js.map +1 -1
  32. package/lib/common/types.js +2 -2
  33. package/lib/common/types.js.map +1 -1
  34. package/lib/common/utils.js.map +1 -1
  35. package/lib/configMeta.js +1 -1
  36. package/lib/configMeta.js.map +1 -1
  37. package/lib/streamer/processors/asyncOpStream.js.map +1 -1
  38. package/lib/streamer/sObjectStream.js.map +1 -1
  39. package/messages/project.deploy.pipeline.quick.md +3 -1
  40. package/messages/project.deploy.pipeline.report.md +2 -0
  41. package/messages/project.deploy.pipeline.resume.md +2 -0
  42. package/messages/project.deploy.pipeline.start.md +2 -0
  43. package/messages/project.deploy.pipeline.validate.md +2 -0
  44. package/npm-shrinkwrap.json +6269 -8073
  45. package/oclif.lock +1847 -2915
  46. package/oclif.manifest.json +14 -26
  47. package/package.json +8 -8
package/messages/project.deploy.pipeline.quick.md CHANGED
@@ -4,7 +4,9 @@ Quickly deploy a validated deployment to an org.
4
4
 
5
5
  # description
6
6
 
7
- 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.
7
+ The first time you run any "project deploy pipeline" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the "org login web" command.
8
+
9
+ Before you run this command, create a validated deployment with the "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.
8
10
 
9
11
  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.
10
12
 
package/messages/project.deploy.pipeline.report.md CHANGED
@@ -4,6 +4,8 @@ Check the status of a pipeline deploy operation.
4
4
 
5
5
  # description
6
6
 
7
+ The first time you run any "project deploy pipeline" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the "org login web" command.
8
+
7
9
  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.
8
10
 
9
11
  # examples
package/messages/project.deploy.pipeline.resume.md CHANGED
@@ -4,6 +4,8 @@ Resume watching a pipeline deploy operation.
4
4
 
5
5
  # description
6
6
 
7
+ The first time you run any "project deploy pipeline" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the "org login web" command.
8
+
7
9
  Use this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.
8
10
 
9
11
  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.
package/messages/project.deploy.pipeline.start.md CHANGED
@@ -4,6 +4,8 @@ Deploy changes from a branch to the pipeline stage’s org.
4
4
 
5
5
  # description
6
6
 
7
+ The first time you run any "project deploy pipeline" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the "org login web" command.
8
+
7
9
  Before you run this command, changes in the pipeline stage's branch must be merged in the source control repository.
8
10
 
9
11
  # examples
package/messages/project.deploy.pipeline.validate.md CHANGED
@@ -4,6 +4,8 @@ Perform a validate-only deployment from a branch to the pipeline stage’s org.
4
4
 
5
5
  # description
6
6
 
7
+ The first time you run any "project deploy pipeline" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the "org login web" command.
8
+
7
9
  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.
8
10
 
9
11
  # examples