From e0f1d0870143700b8239e5d03ed99556a7bf8b81 Mon Sep 17 00:00:00 2001 From: SF-CLI-BOT Date: Thu, 12 Aug 2021 23:06:24 +0000 Subject: [PATCH] chore(release): 1.0.9 [ci skip] --- CHANGELOG.md | 7 ++ README.md | 279 +++++++++++++++++++++++++++++++++++++++++++-------- 2 files changed, 244 insertions(+), 42 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 15f22f162..d717ea4be 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,13 @@ All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. +### [1.0.9](https://github.com/salesforcecli/plugin-source/compare/v1.0.7...v1.0.9) (2021-08-12) + + +### Bug Fixes + +* update command long descriptions ([#174](https://github.com/salesforcecli/plugin-source/issues/174)) ([12f1301](https://github.com/salesforcecli/plugin-source/commit/12f1301bc387f3d7ddcb5f6393bbcf20d038eb1c)) + ### [1.0.7](https://github.com/salesforcecli/plugin-source/compare/v1.0.6...v1.0.7) (2021-08-05) diff --git a/README.md b/README.md index 90a26d761..f9090055a 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ $ npm install -g @salesforce/plugin-source $ sfdx COMMAND running command... $ sfdx (-v|--version|version) -@salesforce/plugin-source/1.0.6 linux-x64 node-v12.22.4 +@salesforce/plugin-source/1.0.9 linux-x64 node-v12.22.5 $ sfdx --help [COMMAND] USAGE $ sfdx COMMAND @@ -95,24 +95,33 @@ USAGE * [`sfdx force:source:deploy [--soapdeploy] [-w ] [-q | -x | -m | -p | -c | -l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg | -r | -o | -g] [-u ] [--apiversion ] [--verbose] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sfdx-forcesourcedeploy---soapdeploy--w-minutes--q-id---x-filepath---m-array---p-array---c---l-notestrunrunspecifiedtestsrunlocaltestsrunalltestsinorg---r-array---o---g--u-string---apiversion-string---verbose---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal) * [`sfdx force:source:deploy:cancel [-w ] [-i ] [-u ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sfdx-forcesourcedeploycancel--w-minutes--i-id--u-string---apiversion-string---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal) * [`sfdx force:source:deploy:report [-w ] [-i ] [-u ] [--apiversion ] [--verbose] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sfdx-forcesourcedeployreport--w-minutes--i-id--u-string---apiversion-string---verbose---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal) +* [`sfdx force:source:manifest:create [-m | -p ] [-n | -t pre|post|destroy|package] [-o ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sfdx-forcesourcemanifestcreate--m-array---p-array--n-string---t-prepostdestroypackage--o-string---apiversion-string---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal) * [`sfdx force:source:open -f [-r] [-u ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sfdx-forcesourceopen--f-filepath--r--u-string---apiversion-string---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal) * [`sfdx force:source:retrieve [-p | -x | -m ] [-w ] [-n ] [-u ] [-a ] [--verbose] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]`](#sfdx-forcesourceretrieve--p-array---x-filepath---m-array--w-minutes--n-array--u-string--a-string---verbose---json---loglevel-tracedebuginfowarnerrorfataltracedebuginfowarnerrorfatal) ## `sfdx force:source:convert [-r ] [-d ] [-n ] [-p | -x | -m ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` -convert source into Metadata API format +convert source into Metadata API format ``` -convert source into Metadata API format +convert source into Metadata API format + Converts source-formatted files into metadata that you can deploy using Metadata API. +To convert source-formatted files into the metadata format, so that you can deploy them using Metadata API, +run "sfdx force:source:convert". Then deploy the metadata using "sfdx force:mdapi:deploy". + +To convert Metadata API–formatted files into the source format, run "sfdx force:mdapi:convert". + +To specify a package name that includes spaces, enclose the name in single quotes. USAGE $ sfdx force:source:convert [-r ] [-d ] [-n ] [-p | -x | -m ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL] OPTIONS - -d, --outputdir=outputdir [default: ./] output directory to - store the Metadata API–formatted - files in + -d, --outputdir=outputdir [default: + metadataPackage_1628809582388] + output directory to store the + Metadata API–formatted files in -m, --metadata=metadata comma-separated list of metadata component names to convert @@ -134,19 +143,38 @@ OPTIONS --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for this command invocation +DESCRIPTION + Converts source-formatted files into metadata that you can deploy using Metadata API. + To convert source-formatted files into the metadata format, so that you can deploy them using Metadata API, + run "sfdx force:source:convert". Then deploy the metadata using "sfdx force:mdapi:deploy". + + To convert Metadata API–formatted files into the source format, run "sfdx force:mdapi:convert". + + To specify a package name that includes spaces, enclose the name in single quotes. + EXAMPLES $ sfdx force:source:convert -r path/to/source $ sfdx force:source:convert -r path/to/source -d path/to/outputdir -n 'My Package' ``` -_See code: [src/commands/force/source/convert.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.6/src/commands/force/source/convert.ts)_ +_See code: [src/commands/force/source/convert.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/convert.ts)_ ## `sfdx force:source:deploy [--soapdeploy] [-w ] [-q | -x | -m | -p | -c | -l NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg | -r | -o | -g] [-u ] [--apiversion ] [--verbose] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` -deploy source to an org +deploy source to an org Use this command to deploy source (metadata that’s in source format) to an org. ``` -deploy source to an org +deploy source to an org Use this command to deploy source (metadata that’s in source format) to an org. +To take advantage of change tracking with scratch orgs, use "sfdx force:source:push". +To deploy metadata that’s in metadata format, use "sfdx force:mdapi:deploy". + +The source you deploy overwrites the corresponding metadata in your org. This command does not attempt to merge your source with the versions in your org. + +To run the command asynchronously, set --wait to 0, which immediately returns the job ID. This way, you can continue to use the CLI. +To check the status of the job, use force:source:deploy:report. + +If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of double quotes. On Windows, if the list contains commas, also enclose the entire list in one set of double quotes. + USAGE $ sfdx force:source:deploy [--soapdeploy] [-w ] [-q | -x | -m | -p | -c | -l @@ -200,21 +228,46 @@ OPTIONS --verbose verbose output of deploy result +DESCRIPTION + To take advantage of change tracking with scratch orgs, use "sfdx force:source:push". + To deploy metadata that’s in metadata format, use "sfdx force:mdapi:deploy". + + The source you deploy overwrites the corresponding metadata in your org. This command does not attempt to merge your + source with the versions in your org. + + To run the command asynchronously, set --wait to 0, which immediately returns the job ID. This way, you can continue + to use the CLI. + To check the status of the job, use force:source:deploy:report. + + If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of + double quotes. On Windows, if the list contains commas, also enclose the entire list in one set of double quotes. + EXAMPLES - $ sfdx force:source:deploy -p path/to/source - $ sfdx force:source:deploy -p "path/to/apex/classes/MyClass.cls,path/to/source/objects" - $ sfdx force:source:deploy -p "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, path/to/apex/classes" - $ sfdx force:source:deploy -m ApexClass - $ sfdx force:source:deploy -m ApexClass:MyApexClass - $ sfdx force:source:deploy -m "CustomObject,ApexClass" - $ sfdx force:source:deploy -m "ApexClass, Profile:My Profile, Profile: AnotherProfile" - $ sfdx force:source:deploy -x path/to/package.xml - $ sfdx force:source:deploy -m ApexClass -l RunLocalTests - $ sfdx force:source:deploy -m ApexClass -l RunAllTestsInOrg -c - $ sfdx force:source:deploy -q 0Af9A00000FTM6pSAH + To deploy the source files in a directory: + $ sfdx force:source:deploy -p path/to/source + To deploy a specific Apex class and the objects whose source is in a directory: + $ sfdx force:source:deploy -p "path/to/apex/classes/MyClass.cls,path/to/source/objects" + To deploy source files in a comma-separated list that contains spaces: + $ sfdx force:source:deploy -p "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, path/to/apex/classes" + To deploy all Apex classes: + $ sfdx force:source:deploy -m ApexClass + To deploy a specific Apex class: + $ sfdx force:source:deploy -m ApexClass:MyApexClass + To deploy all custom objects and Apex classes: + $ sfdx force:source:deploy -m "CustomObject,ApexClass" + To deploy all Apex classes and two specific profiles (one of which has a space in its name): + $ sfdx force:source:deploy -m "ApexClass, Profile:My Profile, Profile: AnotherProfile" + To deploy all components listed in a manifest: + $ sfdx force:source:deploy -x path/to/package.xml + To run the tests that aren’t in any managed packages as part of a deployment: + $ sfdx force:source:deploy -m ApexClass -l RunLocalTests + To check whether a deployment would succeed (to prepare for Quick Deploy): + $ sfdx force:source:deploy -m ApexClass -l RunAllTestsInOrg -c + To deploy an already validated deployment (Quick Deploy): + $ sfdx force:source:deploy -q 0Af9A00000FTM6pSAH`, ``` -_See code: [src/commands/force/source/deploy.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.6/src/commands/force/source/deploy.ts)_ +_See code: [src/commands/force/source/deploy.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/deploy.ts)_ ## `sfdx force:source:deploy:cancel [-w ] [-i ] [-u ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` @@ -222,6 +275,10 @@ cancel a source deployment ``` cancel a source deployment + Use this command to cancel a specified asynchronous source deployment. You can also specify a wait time (in minutes) to check for updates to the canceled deploy status. + +To run the command asynchronously, set --wait to 0, which immediately returns the job ID. This way, you can continue to use the CLI. +To check the status of the job, use force:source:deploy:report. USAGE $ sfdx force:source:deploy:cancel [-w ] [-i ] [-u ] [--apiversion ] [--json] [--loglevel @@ -246,20 +303,34 @@ OPTIONS --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for this command invocation +DESCRIPTION + Use this command to cancel a specified asynchronous source deployment. You can also specify a wait time (in minutes) + to check for updates to the canceled deploy status. + + To run the command asynchronously, set --wait to 0, which immediately returns the job ID. This way, you can continue + to use the CLI. + To check the status of the job, use force:source:deploy:report. + EXAMPLES - $ sfdx force:source:deploy:cancel - $ sfdx force:source:deploy:cancel -w 2 - $ sfdx force:source:deploy:cancel -i + Deploy a directory of files to the org + $ sfdx force:source:deploy -d + Now cancel this deployment and wait two minutes + $ sfdx force:source:deploy:cancel -w 2 + If you have multiple deployments in progress and want to cancel a specific one, specify the job ID + $ sfdx force:source:deploy:cancel -i + Check the status of the cancel job + $ sfdx force:source:deploy:report ``` -_See code: [src/commands/force/source/deploy/cancel.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.6/src/commands/force/source/deploy/cancel.ts)_ +_See code: [src/commands/force/source/deploy/cancel.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/deploy/cancel.ts)_ ## `sfdx force:source:deploy:report [-w ] [-i ] [-u ] [--apiversion ] [--verbose] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` -check the status of a metadata deployment +check the status of a metadata deployment ``` -check the status of a metadata deployment +check the status of a metadata deployment +Specify the job ID for the deploy you want to check. You can also specify a wait time (minutes) to check for updates to the deploy status. USAGE $ sfdx force:source:deploy:report [-w ] [-i ] [-u ] [--apiversion ] [--verbose] [--json] @@ -286,6 +357,10 @@ OPTIONS --verbose verbose output of deploy result +DESCRIPTION + Specify the job ID for the deploy you want to check. You can also specify a wait time (minutes) to check for updates + to the deploy status. + EXAMPLES Deploy a directory of files to the org $ sfdx force:source:deploy -d @@ -297,7 +372,86 @@ EXAMPLES $ sfdx force:source:deploy:report ``` -_See code: [src/commands/force/source/deploy/report.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.6/src/commands/force/source/deploy/report.ts)_ +_See code: [src/commands/force/source/deploy/report.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/deploy/report.ts)_ + +## `sfdx force:source:manifest:create [-m | -p ] [-n | -t pre|post|destroy|package] [-o ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` + +create a project manifest that lists the metadata components you want to deploy or retrieve + +``` +create a project manifest that lists the metadata components you want to deploy or retrieve + Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--sourcepath). You can specify either of these parameters, not both. + +Use --manifesttype to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are: + + package : package.xml (default) + pre : destructiveChangesPre.xml + post : destructiveChangesPost.xml + destroy : destructiveChanges.xml + +See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files. + +Use --manifestname to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifesttype or --manifestname, but not both. + + +USAGE + $ sfdx force:source:manifest:create [-m | -p ] [-n | -t pre|post|destroy|package] [-o + ] [--apiversion ] [--json] [--loglevel + trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL] + +OPTIONS + -m, --metadata=metadata comma-separated list of names of + metadata components to include in + the manifest + + -n, --manifestname=manifestname name of a custom manifest file to + create + + -o, --outputdir=outputdir directory to save the created + manifest + + -p, --sourcepath=sourcepath comma-separated list of paths to the + local source files to include in the + manifest + + -t, --manifesttype=(pre|post|destroy|package) type of manifest to create; the type + determines the name of the created + file + + --apiversion=apiversion override the api version used for + api requests made by this command + + --json format output as json + + --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for + this command invocation + +DESCRIPTION + Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain + source files (--sourcepath). You can specify either of these parameters, not both. + + Use --manifesttype to specify the type of manifest you want to create. The resulting manifest files have specific + names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, + and their respective file names, are: + + package : package.xml (default) + pre : destructiveChangesPre.xml + post : destructiveChangesPost.xml + destroy : destructiveChanges.xml + + See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for + information about these destructive manifest files. + + Use --manifestname to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. + You can specify either --manifesttype or --manifestname, but not both. + +EXAMPLES + $ sfdx force:source:manifest:create -m ApexClass + $ sfdx force:source:manifest:create -m ApexClass:MyApexClass --manifesttype destroy + $ sfdx force:source:manifest:create --sourcepath force-app --manifestname myNewManifest +``` + +_See code: [src/commands/force/source/manifest/create.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/manifest/create.ts)_ ## `sfdx force:source:open -f [-r] [-u ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` @@ -307,6 +461,10 @@ edit a Lightning Page with Lightning App Builder edit a Lightning Page with Lightning App Builder Opens the specified Lightning Page in Lightning App Builder. Lightning Page files have the suffix .flexipage-meta.xml, and are stored in the flexipages directory. If you specify a different type of file, this command opens your org’s home page. +The file opens in your default browser. +If no browser-based editor is available for the selected file, this command opens your org's home page. +To generate a URL for the browser-based editor but not open the editor, use --urlonly. + USAGE $ sfdx force:source:open -f [-r] [-u ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL] @@ -333,20 +491,31 @@ DESCRIPTION and are stored in the flexipages directory. If you specify a different type of file, this command opens your org’s home page. + The file opens in your default browser. + If no browser-based editor is available for the selected file, this command opens your org's home page. + To generate a URL for the browser-based editor but not open the editor, use --urlonly. + EXAMPLES $ sfdx force:source:open -f path/to/source $ sfdx force:source:open -r -f path/to/source $ sfdx force:source:open -f path/to/source -u my-user@my-org.com ``` -_See code: [src/commands/force/source/open.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.6/src/commands/force/source/open.ts)_ +_See code: [src/commands/force/source/open.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/open.ts)_ ## `sfdx force:source:retrieve [-p | -x | -m ] [-w ] [-n ] [-u ] [-a ] [--verbose] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]` -retrieve source from an org +retrieve source from an org ``` -retrieve source from an org +retrieve source from an org +Use this command to retrieve source (metadata that’s in source format) from an org. +To take advantage of change tracking with scratch orgs, use "sfdx force:source:pull". +To retrieve metadata that’s in metadata format, use "sfdx force:mdapi:retrieve". + +The source you retrieve overwrites the corresponding source files in your local project. This command does not attempt to merge the source from your org with your local source files. + +If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of double quotes. On Windows, if the list contains commas, also enclose it in one set of double quotes. USAGE $ sfdx force:source:retrieve [-p | -x | -m ] [-w ] [-n ] [-u ] [-a @@ -381,18 +550,44 @@ OPTIONS --verbose verbose output of retrieve result +DESCRIPTION + Use this command to retrieve source (metadata that’s in source format) from an org. + To take advantage of change tracking with scratch orgs, use "sfdx force:source:pull". + To retrieve metadata that’s in metadata format, use "sfdx force:mdapi:retrieve". + + The source you retrieve overwrites the corresponding source files in your local project. This command does not attempt + to merge the source from your org with your local source files. + + If the comma-separated list you’re supplying contains spaces, enclose the entire comma-separated list in one set of + double quotes. On Windows, if the list contains commas, also enclose it in one set of double quotes. + EXAMPLES - sfdx force:source:retrieve -p path/to/source - sfdx force:source:retrieve -p "path/to/apex/classes/MyClass.cls,path/to/source/objects" - sfdx force:source:retrieve -p "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, path/to/apex/classes" - sfdx force:source:retrieve -m ApexClass - sfdx force:source:retrieve -m ApexClass:MyApexClass - sfdx force:source:retrieve -m "CustomObject,ApexClass" - sfdx force:source:retrieve -x path/to/package.xml - sfdx force:source:retrieve -n "Package1, PackageName With Spaces, Package3" - sfdx force:source:retrieve -n MyPackageName -p path/to/apex/classes - sfdx force:source:retrieve -n MyPackageName -x path/to/package.xml + To retrieve the source files in a directory: + $ sfdx force:source:retrieve -p path/to/source + To retrieve a specific Apex class and the objects whose source is in a directory: + $ sfdx force:source:retrieve -p "path/to/apex/classes/MyClass.cls,path/to/source/objects" + To retrieve source files in a comma-separated list that contains spaces: + $ sfdx force:source:retrieve -p "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, + path/to/apex/classes + To retrieve all Apex classes: + $ sfdx force:source:retrieve -m ApexClass + To retrieve a specific Apex class: + $ sfdx force:source:retrieve -m ApexClass:MyApexClass + To retrieve all custom objects and Apex classes: + $ sfdx force:source:retrieve -m "CustomObject,ApexClass + To retrieve all Apex classes and two specific profiles (one of which has a space in its name): + $ sfdx force:source:retrieve -m "ApexClass, Profile:My Profile, Profile: AnotherProfile" + To retrieve all metadata components listed in a manifest: + $ sfdx force:source:retrieve -x path/to/package.xml + To retrieve metadata from a package or multiple packages: + $ sfdx force:source:retrieve -n MyPackageName + $ sfdx force:source:retrieve -n "Package1, PackageName With Spaces, Package3" + To retrieve all metadata from a package and specific components that aren’t in the package, specify both -n | + --packagenames and one other scoping parameter: + $ sfdx force:source:retrieve -n MyPackageName -p path/to/apex/classes + $ sfdx force:source:retrieve -n MyPackageName -m ApexClass:MyApexClass + $ sfdx force:source:retrieve -n MyPackageName -x path/to/package.xml ``` -_See code: [src/commands/force/source/retrieve.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.6/src/commands/force/source/retrieve.ts)_ +_See code: [src/commands/force/source/retrieve.ts](https://github.com/salesforcecli/plugin-source/blob/v1.0.9/src/commands/force/source/retrieve.ts)_