@salesforce/plugin-deploy-retrieve 1.8.15 → 1.8.17
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.
|
@@ -8,7 +8,7 @@ You must run this command from within a project.
|
|
|
8
8
|
|
|
9
9
|
Metadata components are deployed in source format by default. Deploy them in metadata format by specifying the --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you want to deploy.
|
|
10
10
|
|
|
11
|
-
If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking.
|
|
11
|
+
If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the "<%= config.bin %> org create scratch|sandbox" commands.
|
|
12
12
|
|
|
13
13
|
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.
|
|
14
14
|
|
|
@@ -8,7 +8,7 @@ You must run this command from within a project.
|
|
|
8
8
|
|
|
9
9
|
The command outputs a table that describes what will happen if you run the "<%= config.bin %> project deploy start" command. The table lists the metadata components that will be deployed and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be deployed because they're included in your .forceignore file.
|
|
10
10
|
|
|
11
|
-
If your org allows source tracking, then this command
|
|
11
|
+
If your org allows source tracking, then this command displays potential conflicts between the org and your local project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the "<%= config.bin %> org create scratch|sandbox" commands.
|
|
12
12
|
|
|
13
13
|
To preview 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.
|
|
14
14
|
|
|
@@ -8,7 +8,7 @@ You must run this command from within a project.
|
|
|
8
8
|
|
|
9
9
|
Metadata components are retrieved in source format by default. Retrieve them in metadata format by specifying the --target-metadata-dir flag, which retrieves the components into a ZIP file in the specified directory.
|
|
10
10
|
|
|
11
|
-
If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking.
|
|
11
|
+
If your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the "<%= config.bin %> org create scratch|sandbox" commands.
|
|
12
12
|
|
|
13
13
|
To retrieve multiple metadata components, either use multiple --metadata <name> flags or use 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.
|
|
14
14
|
|
|
@@ -8,7 +8,7 @@ You must run this command from within a project.
|
|
|
8
8
|
|
|
9
9
|
The command outputs a table that describes what will happen if you run the "<%= config.bin %> project retrieve start" command. The table lists the metadata components that will be retrieved and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be retrieved because they're included in your .forceignore file.
|
|
10
10
|
|
|
11
|
-
If your org allows source tracking, then this command
|
|
11
|
+
If your org allows source tracking, then this command displays potential conflicts between the org and your local project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the "<%= config.bin %> org create scratch|sandbox" commands.
|
|
12
12
|
|
|
13
13
|
# examples
|
|
14
14
|
|
package/oclif.manifest.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "1.8.
|
|
2
|
+
"version": "1.8.17",
|
|
3
3
|
"commands": {
|
|
4
4
|
"deploy": {
|
|
5
5
|
"id": "deploy",
|
|
@@ -203,7 +203,7 @@
|
|
|
203
203
|
"char": "d",
|
|
204
204
|
"summary": "Output directory to store the Metadata API–formatted files in.",
|
|
205
205
|
"multiple": false,
|
|
206
|
-
"default": "
|
|
206
|
+
"default": "metadataPackage_1682535747249",
|
|
207
207
|
"deprecateAliases": true,
|
|
208
208
|
"aliases": [
|
|
209
209
|
"outputdir"
|
|
@@ -586,7 +586,7 @@
|
|
|
586
586
|
"project:deploy:preview": {
|
|
587
587
|
"id": "project:deploy:preview",
|
|
588
588
|
"summary": "Preview a deployment to see what will deploy to the org, the potential conflicts, and the ignored files.",
|
|
589
|
-
"description": "You must run this command from within a project.\n\nThe command outputs a table that describes what will happen if you run the \"<%= config.bin %> project deploy start\" command. The table lists the metadata components that will be deployed and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be deployed because they're included in your .forceignore file.\n\nIf your org allows source tracking, then this command
|
|
589
|
+
"description": "You must run this command from within a project.\n\nThe command outputs a table that describes what will happen if you run the \"<%= config.bin %> project deploy start\" command. The table lists the metadata components that will be deployed and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be deployed because they're included in your .forceignore file.\n\nIf your org allows source tracking, then this command displays potential conflicts between the org and your local project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo preview 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.",
|
|
590
590
|
"strict": true,
|
|
591
591
|
"pluginName": "@salesforce/plugin-deploy-retrieve",
|
|
592
592
|
"pluginAlias": "@salesforce/plugin-deploy-retrieve",
|
|
@@ -1065,7 +1065,7 @@
|
|
|
1065
1065
|
"project:deploy:start": {
|
|
1066
1066
|
"id": "project:deploy:start",
|
|
1067
1067
|
"summary": "Deploy metadata to an org from your local project.",
|
|
1068
|
-
"description": "You must run this command from within a project.\n\nMetadata components are deployed in source format by default. Deploy them in metadata format by specifying the --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you want to deploy.\n\nIf your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking.
|
|
1068
|
+
"description": "You must run this command from within a project.\n\nMetadata components are deployed in source format by default. Deploy them in metadata format by specifying the --metadata-dir flag, which specifies the root directory or ZIP file that contains the metadata formatted files you want to deploy.\n\nIf your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo 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.",
|
|
1069
1069
|
"strict": true,
|
|
1070
1070
|
"pluginName": "@salesforce/plugin-deploy-retrieve",
|
|
1071
1071
|
"pluginAlias": "@salesforce/plugin-deploy-retrieve",
|
|
@@ -1906,7 +1906,7 @@
|
|
|
1906
1906
|
"project:retrieve:preview": {
|
|
1907
1907
|
"id": "project:retrieve:preview",
|
|
1908
1908
|
"summary": "Preview a retrieval to see what will be retrieved from the org, the potential conflicts, and the ignored files.",
|
|
1909
|
-
"description": "You must run this command from within a project.\n\nThe command outputs a table that describes what will happen if you run the \"<%= config.bin %> project retrieve start\" command. The table lists the metadata components that will be retrieved and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be retrieved because they're included in your .forceignore file.\n\nIf your org allows source tracking, then this command
|
|
1909
|
+
"description": "You must run this command from within a project.\n\nThe command outputs a table that describes what will happen if you run the \"<%= config.bin %> project retrieve start\" command. The table lists the metadata components that will be retrieved and deleted. The table also lists the current conflicts between files in your local project and components in the org. Finally, the table lists the files that won't be retrieved because they're included in your .forceignore file.\n\nIf your org allows source tracking, then this command displays potential conflicts between the org and your local project. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.",
|
|
1910
1910
|
"strict": true,
|
|
1911
1911
|
"pluginName": "@salesforce/plugin-deploy-retrieve",
|
|
1912
1912
|
"pluginAlias": "@salesforce/plugin-deploy-retrieve",
|
|
@@ -1955,7 +1955,7 @@
|
|
|
1955
1955
|
"project:retrieve:start": {
|
|
1956
1956
|
"id": "project:retrieve:start",
|
|
1957
1957
|
"summary": "Retrieve metadata from an org to your local project.",
|
|
1958
|
-
"description": "You must run this command from within a project.\n\nMetadata components are retrieved in source format by default. Retrieve them in metadata format by specifying the --target-metadata-dir flag, which retrieves the components into a ZIP file in the specified directory.\n\nIf your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking.
|
|
1958
|
+
"description": "You must run this command from within a project.\n\nMetadata components are retrieved in source format by default. Retrieve them in metadata format by specifying the --target-metadata-dir flag, which retrieves the components into a ZIP file in the specified directory.\n\nIf your org allows source tracking, then this command tracks the changes in your source. Some orgs, such as production org, never allow source tracking. Source tracking is enabled by default on scratch and sandbox orgs; you can disable source tracking when you create the orgs by specifying the --no-track-source flag on the \"<%= config.bin %> org create scratch|sandbox\" commands.\n\nTo retrieve multiple metadata components, either use multiple --metadata <name> flags or use 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.",
|
|
1959
1959
|
"strict": true,
|
|
1960
1960
|
"pluginName": "@salesforce/plugin-deploy-retrieve",
|
|
1961
1961
|
"pluginAlias": "@salesforce/plugin-deploy-retrieve",
|
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": "1.8.
|
|
4
|
+
"version": "1.8.17",
|
|
5
5
|
"author": "Salesforce",
|
|
6
6
|
"bugs": "https://github.com/forcedotcom/cli/issues",
|
|
7
7
|
"dependencies": {
|
|
@@ -25,8 +25,8 @@
|
|
|
25
25
|
"@salesforce/plugin-command-reference": "^2.4.1",
|
|
26
26
|
"@salesforce/plugin-functions": "^1.21.6",
|
|
27
27
|
"@salesforce/plugin-settings": "^1.4.2",
|
|
28
|
-
"@salesforce/plugin-source": "^2.10.
|
|
29
|
-
"@salesforce/plugin-templates": "^55.4.
|
|
28
|
+
"@salesforce/plugin-source": "^2.10.4",
|
|
29
|
+
"@salesforce/plugin-templates": "^55.4.10",
|
|
30
30
|
"@salesforce/plugin-user": "^2.3.6",
|
|
31
31
|
"@salesforce/prettier-config": "^0.0.2",
|
|
32
32
|
"@salesforce/source-testkit": "^2.0.43",
|
|
@@ -49,10 +49,10 @@
|
|
|
49
49
|
"eslint-plugin-jsdoc": "^39.9.1",
|
|
50
50
|
"eslint-plugin-sf-plugin": "^1.15.1",
|
|
51
51
|
"husky": "^7.0.4",
|
|
52
|
-
"jsforce": "^2.0.0-beta.
|
|
52
|
+
"jsforce": "^2.0.0-beta.21",
|
|
53
53
|
"mocha": "^10.1.0",
|
|
54
54
|
"nyc": "^15.1.0",
|
|
55
|
-
"oclif": "^3.
|
|
55
|
+
"oclif": "^3.8.1",
|
|
56
56
|
"prettier": "^2.8.4",
|
|
57
57
|
"pretty-quick": "^3.1.3",
|
|
58
58
|
"shx": "0.3.4",
|
|
@@ -270,7 +270,7 @@
|
|
|
270
270
|
}
|
|
271
271
|
},
|
|
272
272
|
"sfdx": {
|
|
273
|
-
"publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.
|
|
274
|
-
"signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.
|
|
273
|
+
"publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.17.crt",
|
|
274
|
+
"signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-deploy-retrieve/1.8.17.sig"
|
|
275
275
|
}
|
|
276
276
|
}
|