@salesforce/plugin-deploy-retrieve 3.24.1 → 3.24.3
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.
- package/LICENSE.txt +1 -1
- package/README.md +53 -23
- package/lib/commands/project/convert/mdapi.js +1 -1
- package/lib/commands/project/convert/source-behavior.js +1 -1
- package/lib/commands/project/convert/source.js +1 -1
- package/lib/commands/project/delete/source.js +1 -1
- package/lib/commands/project/delete/tracking.js +1 -1
- package/lib/commands/project/deploy/cancel.js +1 -1
- package/lib/commands/project/deploy/preview.js +1 -1
- package/lib/commands/project/deploy/quick.js +1 -1
- package/lib/commands/project/deploy/report.js +1 -1
- package/lib/commands/project/deploy/resume.js +1 -1
- package/lib/commands/project/deploy/start.js +1 -1
- package/lib/commands/project/deploy/validate.js +1 -1
- package/lib/commands/project/generate/manifest.js +1 -1
- package/lib/commands/project/list/ignored.js +1 -1
- package/lib/commands/project/reset/tracking.js +1 -1
- package/lib/commands/project/retrieve/preview.js +1 -1
- package/lib/commands/project/retrieve/start.js +1 -1
- package/lib/configMeta.js +1 -1
- package/lib/formatters/asyncDeployCancelResultFormatter.js +1 -1
- package/lib/formatters/asyncDeployResultFormatter.js +1 -1
- package/lib/formatters/deleteResultFormatter.js +1 -1
- package/lib/formatters/deployCancelResultFormatter.js +1 -1
- package/lib/formatters/deployReportResultFormatter.js +1 -1
- package/lib/formatters/deployResultFormatter.js +1 -1
- package/lib/formatters/metadataConvertResultFormatter.js +1 -1
- package/lib/formatters/metadataRetrieveResultFormatter.js +1 -1
- package/lib/formatters/retrieveResultFormatter.js +1 -1
- package/lib/formatters/sourceConvertResultFormatter.js +1 -1
- package/lib/formatters/testResultsFormatter.js +1 -1
- package/lib/hooks/diagnostics.js +1 -1
- package/lib/index.js +1 -1
- package/lib/utils/conflicts.js +1 -1
- package/lib/utils/convertBehavior.js +1 -1
- package/lib/utils/coverage.js +1 -1
- package/lib/utils/deploy.js +1 -1
- package/lib/utils/deployCache.js +1 -1
- package/lib/utils/deployStages.js +1 -1
- package/lib/utils/errorCodes.js +1 -1
- package/lib/utils/flags.js +1 -1
- package/lib/utils/manifestCache.js +1 -1
- package/lib/utils/metadataTypes.js +1 -1
- package/lib/utils/output.js +1 -1
- package/lib/utils/previewOutput.js +1 -1
- package/lib/utils/project.js +1 -1
- package/lib/utils/promiseQueue.js +1 -1
- package/lib/utils/types.js +1 -1
- package/messages/delete.source.md +3 -1
- package/messages/deploy.metadata.md +2 -2
- package/messages/deploy.metadata.validate.md +3 -1
- package/oclif.manifest.json +4 -4
- package/package.json +5 -5
package/LICENSE.txt
CHANGED
package/README.md
CHANGED
|
@@ -141,7 +141,7 @@ FLAG DESCRIPTIONS
|
|
|
141
141
|
If you specify this flag, don’t specify --metadata or --source-dir.
|
|
142
142
|
```
|
|
143
143
|
|
|
144
|
-
_See code: [src/commands/project/convert/mdapi.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
144
|
+
_See code: [src/commands/project/convert/mdapi.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/convert/mdapi.ts)_
|
|
145
145
|
|
|
146
146
|
## `sf project convert source`
|
|
147
147
|
|
|
@@ -214,7 +214,7 @@ FLAG DESCRIPTIONS
|
|
|
214
214
|
Override the api version used for api requests made by this command
|
|
215
215
|
```
|
|
216
216
|
|
|
217
|
-
_See code: [src/commands/project/convert/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
217
|
+
_See code: [src/commands/project/convert/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/convert/source.ts)_
|
|
218
218
|
|
|
219
219
|
## `sf project convert source-behavior`
|
|
220
220
|
|
|
@@ -273,7 +273,7 @@ EXAMPLES
|
|
|
273
273
|
$ sf project convert source-behavior --behavior decomposePermissionSetBeta --dry-run --preserve-temp-dir
|
|
274
274
|
```
|
|
275
275
|
|
|
276
|
-
_See code: [src/commands/project/convert/source-behavior.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
276
|
+
_See code: [src/commands/project/convert/source-behavior.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/convert/source-behavior.ts)_
|
|
277
277
|
|
|
278
278
|
## `sf project delete source`
|
|
279
279
|
|
|
@@ -388,8 +388,19 @@ FLAG DESCRIPTIONS
|
|
|
388
388
|
|
|
389
389
|
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
|
|
390
390
|
|
|
391
|
+
- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically
|
|
392
|
+
identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For
|
|
393
|
+
fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest
|
|
394
|
+
Annotation" in the "Apex Developer Guide"
|
|
395
|
+
(https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each
|
|
396
|
+
class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code
|
|
397
|
+
coverage. This coverage is computed for each class and triggers individually and is different than the overall
|
|
398
|
+
coverage percentage.
|
|
399
|
+
|
|
391
400
|
If you don’t specify a test level, the default behavior depends on the contents of your deployment package and
|
|
392
|
-
target org. For more information, see
|
|
401
|
+
target org. For more information, see "Running Tests in a Deployment"
|
|
402
|
+
(https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the
|
|
403
|
+
"Metadata API Developer Guide".
|
|
393
404
|
|
|
394
405
|
-m, --metadata=<value>... Metadata components to delete.
|
|
395
406
|
|
|
@@ -415,7 +426,7 @@ FLAG DESCRIPTIONS
|
|
|
415
426
|
- Separate the test names with spaces: --tests Test1 Test2 "Test With Space"
|
|
416
427
|
```
|
|
417
428
|
|
|
418
|
-
_See code: [src/commands/project/delete/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
429
|
+
_See code: [src/commands/project/delete/source.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/delete/source.ts)_
|
|
419
430
|
|
|
420
431
|
## `sf project delete tracking`
|
|
421
432
|
|
|
@@ -452,7 +463,7 @@ EXAMPLES
|
|
|
452
463
|
$ sf project delete tracking --target-org my-scratch
|
|
453
464
|
```
|
|
454
465
|
|
|
455
|
-
_See code: [src/commands/project/delete/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
466
|
+
_See code: [src/commands/project/delete/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/delete/tracking.ts)_
|
|
456
467
|
|
|
457
468
|
## `sf project deploy cancel`
|
|
458
469
|
|
|
@@ -524,7 +535,7 @@ FLAG DESCRIPTIONS
|
|
|
524
535
|
project deploy report".
|
|
525
536
|
```
|
|
526
537
|
|
|
527
|
-
_See code: [src/commands/project/deploy/cancel.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
538
|
+
_See code: [src/commands/project/deploy/cancel.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/cancel.ts)_
|
|
528
539
|
|
|
529
540
|
## `sf project deploy preview`
|
|
530
541
|
|
|
@@ -607,7 +618,7 @@ FLAG DESCRIPTIONS
|
|
|
607
618
|
All child components are included. If you specify this flag, don’t specify --metadata or --source-dir.
|
|
608
619
|
```
|
|
609
620
|
|
|
610
|
-
_See code: [src/commands/project/deploy/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
621
|
+
_See code: [src/commands/project/deploy/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/preview.ts)_
|
|
611
622
|
|
|
612
623
|
## `sf project deploy quick`
|
|
613
624
|
|
|
@@ -691,7 +702,7 @@ FLAG DESCRIPTIONS
|
|
|
691
702
|
deploy report".
|
|
692
703
|
```
|
|
693
704
|
|
|
694
|
-
_See code: [src/commands/project/deploy/quick.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
705
|
+
_See code: [src/commands/project/deploy/quick.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/quick.ts)_
|
|
695
706
|
|
|
696
707
|
## `sf project deploy report`
|
|
697
708
|
|
|
@@ -783,7 +794,7 @@ FLAG DESCRIPTIONS
|
|
|
783
794
|
--coverage-formatters lcov --coverage-formatters clover
|
|
784
795
|
```
|
|
785
796
|
|
|
786
|
-
_See code: [src/commands/project/deploy/report.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
797
|
+
_See code: [src/commands/project/deploy/report.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/report.ts)_
|
|
787
798
|
|
|
788
799
|
## `sf project deploy resume`
|
|
789
800
|
|
|
@@ -868,7 +879,7 @@ FLAG DESCRIPTIONS
|
|
|
868
879
|
--coverage-formatters lcov --coverage-formatters clover
|
|
869
880
|
```
|
|
870
881
|
|
|
871
|
-
_See code: [src/commands/project/deploy/resume.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
882
|
+
_See code: [src/commands/project/deploy/resume.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/resume.ts)_
|
|
872
883
|
|
|
873
884
|
## `sf project deploy start`
|
|
874
885
|
|
|
@@ -1066,12 +1077,19 @@ FLAG DESCRIPTIONS
|
|
|
1066
1077
|
|
|
1067
1078
|
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
|
|
1068
1079
|
|
|
1069
|
-
- RunRelevantTests — Runs only tests that are relevant to the files being deployed.
|
|
1080
|
+
- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically
|
|
1081
|
+
identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For
|
|
1082
|
+
fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest
|
|
1083
|
+
Annotation" in the "Apex Developer Guide"
|
|
1084
|
+
(https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each
|
|
1085
|
+
class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code
|
|
1086
|
+
coverage. This coverage is computed for each class and triggers individually and is different than the overall
|
|
1087
|
+
coverage percentage.
|
|
1070
1088
|
|
|
1071
1089
|
If you don’t specify a test level, the default behavior depends on the contents of your deployment package and
|
|
1072
|
-
target org. For more information, see
|
|
1073
|
-
|
|
1074
|
-
|
|
1090
|
+
target org. For more information, see "Running Tests in a Deployment"
|
|
1091
|
+
(https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the
|
|
1092
|
+
"Metadata API Developer Guide".
|
|
1075
1093
|
|
|
1076
1094
|
-r, --ignore-errors Ignore any errors and don’t roll back deployment.
|
|
1077
1095
|
|
|
@@ -1110,7 +1128,7 @@ FLAG DESCRIPTIONS
|
|
|
1110
1128
|
--coverage-formatters lcov --coverage-formatters clover
|
|
1111
1129
|
```
|
|
1112
1130
|
|
|
1113
|
-
_See code: [src/commands/project/deploy/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1131
|
+
_See code: [src/commands/project/deploy/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/start.ts)_
|
|
1114
1132
|
|
|
1115
1133
|
## `sf project deploy validate`
|
|
1116
1134
|
|
|
@@ -1251,7 +1269,19 @@ FLAG DESCRIPTIONS
|
|
|
1251
1269
|
|
|
1252
1270
|
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
|
|
1253
1271
|
|
|
1254
|
-
- RunRelevantTests — Runs only tests that are relevant to the files being deployed.
|
|
1272
|
+
- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically
|
|
1273
|
+
identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For
|
|
1274
|
+
fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest
|
|
1275
|
+
Annotation" in the "Apex Developer Guide"
|
|
1276
|
+
(https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each
|
|
1277
|
+
class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code
|
|
1278
|
+
coverage. This coverage is computed for each class and triggers individually and is different than the overall
|
|
1279
|
+
coverage percentage.
|
|
1280
|
+
|
|
1281
|
+
If you don’t specify a test level, the default behavior depends on the contents of your deployment package and
|
|
1282
|
+
target org. For more information, see "Running Tests in a Deployment"
|
|
1283
|
+
(https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the
|
|
1284
|
+
"Metadata API Developer Guide".
|
|
1255
1285
|
|
|
1256
1286
|
-t, --tests=<value>... Apex tests to run when --test-level is RunSpecifiedTests.
|
|
1257
1287
|
|
|
@@ -1285,7 +1315,7 @@ FLAG DESCRIPTIONS
|
|
|
1285
1315
|
--coverage-formatters lcov --coverage-formatters clover
|
|
1286
1316
|
```
|
|
1287
1317
|
|
|
1288
|
-
_See code: [src/commands/project/deploy/validate.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1318
|
+
_See code: [src/commands/project/deploy/validate.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/deploy/validate.ts)_
|
|
1289
1319
|
|
|
1290
1320
|
## `sf project generate manifest`
|
|
1291
1321
|
|
|
@@ -1381,7 +1411,7 @@ EXAMPLES
|
|
|
1381
1411
|
$ sf project generate manifest --from-org test@myorg.com --excluded-metadata StandardValueSet
|
|
1382
1412
|
```
|
|
1383
1413
|
|
|
1384
|
-
_See code: [src/commands/project/generate/manifest.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1414
|
+
_See code: [src/commands/project/generate/manifest.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/generate/manifest.ts)_
|
|
1385
1415
|
|
|
1386
1416
|
## `sf project list ignored`
|
|
1387
1417
|
|
|
@@ -1423,7 +1453,7 @@ EXAMPLES
|
|
|
1423
1453
|
$ sf project list ignored --source-dir package.xml
|
|
1424
1454
|
```
|
|
1425
1455
|
|
|
1426
|
-
_See code: [src/commands/project/list/ignored.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1456
|
+
_See code: [src/commands/project/list/ignored.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/list/ignored.ts)_
|
|
1427
1457
|
|
|
1428
1458
|
## `sf project reset tracking`
|
|
1429
1459
|
|
|
@@ -1472,7 +1502,7 @@ EXAMPLES
|
|
|
1472
1502
|
$ sf project reset tracking --revision 30
|
|
1473
1503
|
```
|
|
1474
1504
|
|
|
1475
|
-
_See code: [src/commands/project/reset/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1505
|
+
_See code: [src/commands/project/reset/tracking.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/reset/tracking.ts)_
|
|
1476
1506
|
|
|
1477
1507
|
## `sf project retrieve preview`
|
|
1478
1508
|
|
|
@@ -1526,7 +1556,7 @@ FLAG DESCRIPTIONS
|
|
|
1526
1556
|
production orgs.
|
|
1527
1557
|
```
|
|
1528
1558
|
|
|
1529
|
-
_See code: [src/commands/project/retrieve/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1559
|
+
_See code: [src/commands/project/retrieve/preview.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/retrieve/preview.ts)_
|
|
1530
1560
|
|
|
1531
1561
|
## `sf project retrieve start`
|
|
1532
1562
|
|
|
@@ -1699,6 +1729,6 @@ FLAG DESCRIPTIONS
|
|
|
1699
1729
|
If you specify this flag, don’t specify --metadata or --source-dir.
|
|
1700
1730
|
```
|
|
1701
1731
|
|
|
1702
|
-
_See code: [src/commands/project/retrieve/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.
|
|
1732
|
+
_See code: [src/commands/project/retrieve/start.ts](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/3.24.3/src/commands/project/retrieve/start.ts)_
|
|
1703
1733
|
|
|
1704
1734
|
<!-- commandsstop -->
|
package/lib/configMeta.js
CHANGED
package/lib/hooks/diagnostics.js
CHANGED
package/lib/index.js
CHANGED
package/lib/utils/conflicts.js
CHANGED
package/lib/utils/coverage.js
CHANGED
package/lib/utils/deploy.js
CHANGED
package/lib/utils/deployCache.js
CHANGED
package/lib/utils/errorCodes.js
CHANGED
package/lib/utils/flags.js
CHANGED
package/lib/utils/output.js
CHANGED
package/lib/utils/project.js
CHANGED
package/lib/utils/types.js
CHANGED
|
@@ -106,7 +106,9 @@ Valid values are:
|
|
|
106
106
|
|
|
107
107
|
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
|
|
108
108
|
|
|
109
|
-
|
|
109
|
+
- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.
|
|
110
|
+
|
|
111
|
+
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".
|
|
110
112
|
|
|
111
113
|
# localPrompt
|
|
112
114
|
|
|
@@ -104,9 +104,9 @@ Valid values are:
|
|
|
104
104
|
|
|
105
105
|
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
|
|
106
106
|
|
|
107
|
-
- RunRelevantTests — Runs only tests that are relevant to the files being deployed.
|
|
107
|
+
- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.
|
|
108
108
|
|
|
109
|
-
|
|
109
|
+
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".
|
|
110
110
|
|
|
111
111
|
# flags.source-dir.summary
|
|
112
112
|
|
|
@@ -52,7 +52,9 @@ Valid values are:
|
|
|
52
52
|
|
|
53
53
|
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
|
|
54
54
|
|
|
55
|
-
- RunRelevantTests — Runs only tests that are relevant to the files being deployed.
|
|
55
|
+
- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.
|
|
56
|
+
|
|
57
|
+
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".
|
|
56
58
|
|
|
57
59
|
# flags.source-dir.summary
|
|
58
60
|
|
package/oclif.manifest.json
CHANGED
|
@@ -506,7 +506,7 @@
|
|
|
506
506
|
],
|
|
507
507
|
"char": "l",
|
|
508
508
|
"deprecateAliases": true,
|
|
509
|
-
"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 --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 and target org. For more information, see
|
|
509
|
+
"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 --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\n- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See \"@IsTest Annotation\" in the \"Apex Developer Guide\" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.\n\nIf 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\".",
|
|
510
510
|
"helpGroup": "Test",
|
|
511
511
|
"name": "test-level",
|
|
512
512
|
"summary": "Deployment Apex testing level.",
|
|
@@ -1690,7 +1690,7 @@
|
|
|
1690
1690
|
},
|
|
1691
1691
|
"test-level": {
|
|
1692
1692
|
"char": "l",
|
|
1693
|
-
"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 --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\n- RunRelevantTests — Runs only tests that are relevant to the files being deployed.\n\
|
|
1693
|
+
"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 --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\n- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See \"@IsTest Annotation\" in the \"Apex Developer Guide\" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.\n\nIf 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\".",
|
|
1694
1694
|
"helpGroup": "Test",
|
|
1695
1695
|
"name": "test-level",
|
|
1696
1696
|
"summary": "Deployment Apex testing level.",
|
|
@@ -2027,7 +2027,7 @@
|
|
|
2027
2027
|
},
|
|
2028
2028
|
"test-level": {
|
|
2029
2029
|
"char": "l",
|
|
2030
|
-
"description": "Valid values are:\n\n- 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.\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.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\n- RunRelevantTests — Runs only tests that are relevant to the files being deployed.",
|
|
2030
|
+
"description": "Valid values are:\n\n- 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.\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.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\n- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See \"@IsTest Annotation\" in the \"Apex Developer Guide\" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.\n\nIf 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\".",
|
|
2031
2031
|
"helpGroup": "Test",
|
|
2032
2032
|
"name": "test-level",
|
|
2033
2033
|
"summary": "Deployment Apex testing level.",
|
|
@@ -3054,5 +3054,5 @@
|
|
|
3054
3054
|
]
|
|
3055
3055
|
}
|
|
3056
3056
|
},
|
|
3057
|
-
"version": "3.24.
|
|
3057
|
+
"version": "3.24.3"
|
|
3058
3058
|
}
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@salesforce/plugin-deploy-retrieve",
|
|
3
3
|
"description": "deploy and retrieve commands for sf",
|
|
4
|
-
"version": "3.24.
|
|
4
|
+
"version": "3.24.3",
|
|
5
5
|
"author": "Salesforce",
|
|
6
6
|
"bugs": "https://github.com/forcedotcom/cli/issues",
|
|
7
7
|
"dependencies": {
|
|
@@ -13,8 +13,8 @@
|
|
|
13
13
|
"@salesforce/kit": "^3.2.4",
|
|
14
14
|
"@salesforce/plugin-info": "^3.4.93",
|
|
15
15
|
"@salesforce/sf-plugins-core": "^12.2.5",
|
|
16
|
-
"@salesforce/source-deploy-retrieve": "^12.
|
|
17
|
-
"@salesforce/source-tracking": "^7.
|
|
16
|
+
"@salesforce/source-deploy-retrieve": "^12.31.1",
|
|
17
|
+
"@salesforce/source-tracking": "^7.8.0",
|
|
18
18
|
"@salesforce/ts-types": "^2.0.12",
|
|
19
19
|
"ansis": "^3.17.0",
|
|
20
20
|
"terminal-link": "^3.0.0"
|
|
@@ -255,7 +255,7 @@
|
|
|
255
255
|
"exports": "./lib/index.js",
|
|
256
256
|
"type": "module",
|
|
257
257
|
"sfdx": {
|
|
258
|
-
"publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.
|
|
259
|
-
"signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.
|
|
258
|
+
"publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.3.crt",
|
|
259
|
+
"signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/3.24.3.sig"
|
|
260
260
|
}
|
|
261
261
|
}
|