You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/deploy.metadata.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,6 +154,14 @@ Run the command asynchronously.
154
154
155
155
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".
156
156
157
+
# flags.metadata-dir.summary
158
+
159
+
Root of directory or zip file of metadata formatted files to deploy.
160
+
161
+
# flags.single-package.summary
162
+
163
+
Indicates that the metadata zip file points to a directory structure for a single package.
Copy file name to clipboardExpand all lines: messages/deploy.metadata.validate.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ To validate the deployment of multiple metadata components, either set multiple
14
14
15
15
# examples
16
16
17
-
- 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.
17
+
- 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.
18
18
19
19
- Validate the deployment of all source files in a directory to the default org:
20
20
@@ -53,9 +53,9 @@ Valid values are:
53
53
- 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.
54
54
55
55
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
56
-
56
+
57
57
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".
58
-
58
+
59
59
# flags.source-dir.summary
60
60
61
61
Path to the local source files to validate for deployment.
@@ -114,6 +114,14 @@ Run the command asynchronously.
114
114
115
115
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".
116
116
117
+
# flags.metadata-dir.summary
118
+
119
+
Root of directory or zip file of metadata formatted files to deploy.
120
+
121
+
# flags.single-package.summary
122
+
123
+
Indicates that the metadata zip file points to a directory structure for a single package.
0 commit comments