Skip to content

Commit

Permalink
chore(release): 0.0.23 [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
SF-CLI-BOT committed Jul 15, 2021
1 parent ee9e786 commit 50fecbd
Show file tree
Hide file tree
Showing 4 changed files with 153 additions and 154 deletions.
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.

### [0.0.23](https://github.com/salesforcecli/cli/compare/v0.0.22...v0.0.23) (2021-07-15)


### Bug Fixes

* update to renamed packages ([#16](https://github.com/salesforcecli/cli/issues/16)) ([ee9e786](https://github.com/salesforcecli/cli/commit/ee9e786ee81fa57bc998a00b006b298fa3bde048))

### [0.0.22](https://github.com/salesforcecli/cli/compare/v0.0.21...v0.0.22) (2021-07-15)

### [0.0.21](https://github.com/salesforcecli/cli/compare/v0.0.20...v0.0.21) (2021-07-14)
Expand Down
276 changes: 139 additions & 137 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,8 @@ USAGE
# Commands

<!-- commands -->
* [`sf deploy`](#sf-deploy)
* [`sf deploy metadata`](#sf-deploy-metadata)
* [`sf env display`](#sf-env-display)
* [`sf env list`](#sf-env-list)
* [`sf env open`](#sf-env-open)
Expand All @@ -46,9 +48,140 @@ USAGE
* [`sf plugins:link PLUGIN`](#sf-pluginslink-plugin)
* [`sf plugins:uninstall PLUGIN...`](#sf-pluginsuninstall-plugin)
* [`sf plugins update`](#sf-plugins-update)
* [`sf project deploy`](#sf-project-deploy)
* [`sf project deploy org`](#sf-project-deploy-org)
* [`sf project retrieve org`](#sf-project-retrieve-org)
* [`sf retrieve metadata`](#sf-retrieve-metadata)

## `sf deploy`

The command first analyzes your project, active or logged-into environments, and local defaults to determine what to deploy and where. The command then prompts you for information about this particular deployment and provides intelligent choices based on its analysis.

```
USAGE
$ sf deploy [--interactive]
FLAGS
--interactive Force the CLI to prompt for all deployment inputs.
DESCRIPTION
Deploy a project interactively to any Salesforce environment.
The command first analyzes your project, active or logged-into environments, and local defaults to determine what to
deploy and where. The command then prompts you for information about this particular deployment and provides
intelligent choices based on its analysis.
For example, if your local project contains a package directory with metadata source files, the command asks if you
want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want to
deploy to. If the command finds Apex tests, it asks if you want to run them and at which level.
Similarly, if the command finds a local functions directory, the command prompts if you want to deploy it and to which
compute environment. The command prompts and connects you to a compute environment of your choice if you’re not
currently connected to any.
This command must be run from within a project.
The command stores your responses in a local file and uses them as defaults when you rerun the command. Specify
--interactive to force the command to reprompt.
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific
commands, such as "sf project deploy org", that provide additional flags.
EXAMPLES
$ sf deploy
```

_See code: [@salesforce/plugin-deploy-retrieve](https://github.com/salesforcecli/plugin-deploy-retrieve/blob/v0.0.8/src/commands/deploy.ts)_

## `sf deploy metadata`

You must run this command from wihin a project.

```
USAGE
$ sf deploy metadata [--json] [-m <value>] [-x <value>] [-d <value>] [--target-org <value>] [-l
NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [--wait <value>]
FLAGS
-d, --deploy-dir=<value>... Root of local directory tree of files to deploy.
-l, --test-level=<option> [default: NoTestRun] Deployment Apex testing level.
<options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
-m, --metadata=<value>... List of metadata component names to deploy.
-x, --manifest=<value> Full file path for manifest (package.xml) of components to deploy.
--target-org=<value> Username or alias of the org you want to deploy to
--wait=<value> [default: 33] Number of minutes to wait for command to complete.
GLOBAL FLAGS
--json format output as json
DESCRIPTION
Deploy source to an org.
You must run this command from wihin a project.
The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your
source with the versions in your org.
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
Deploy the source files in a directory:
$ sf deploy metadata --deploy-dir path/to/source
Deploy a specific Apex class and the objects whose source is in a directory:
$ sf deploy metadata --deploy-dir "path/to/apex/classes/MyClass.cls,path/to/source/objects"
Deploy source files in a comma-separated list that contains spaces:
$ sf deploy metadata --deploy-dir "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, \
path/to/apex/classes"
Deploy all Apex classes:
$ sf deploy metadata --metadata ApexClass
Deploy a specific Apex class:
$ sf deploy metadata --metadata ApexClass:MyApexClass
Deploy all custom objects and Apex classes:
$ sf deploy metadata --metadata "CustomObject,ApexClass"
Deploy all Apex classes and two specific profiles (one of which has a space in its name):
$ sf deploy metadata --metadata "ApexClass, Profile:My Profile, Profile: AnotherProfile"
Deploy all components listed in a manifest:
$ sf deploy metadata --manifest path/to/package.xml
FLAG DESCRIPTIONS
-d, --deploy-dir=<value>... Root of local directory tree of files to deploy.
Root of local directory tree of files to deploy.
-l, --test-level=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg Deployment Apex testing level.
Deployment Apex testing level.
-m, --metadata=<value>... List of metadata component names to deploy.
List of metadata component names to deploy.
-x, --manifest=<value> Full file path for manifest (package.xml) of components to deploy.
Full file path for manifest (package.xml) of components to deploy.
--wait=<value> Number of minutes to wait for command to complete.
Default is 33 minutes.
```

## `sf env display`

Expand Down Expand Up @@ -567,145 +700,14 @@ DESCRIPTION
update installed plugins
```

## `sf project deploy`

The command first analyzes your project, active or logged-into environments, and local defaults to determine what to deploy and where. The command then prompts you for information about this particular deployment and provides intelligent choices based on its analysis.

```
USAGE
$ sf project deploy [--interactive]
FLAGS
--interactive Force the CLI to prompt for all deployment inputs.
DESCRIPTION
Deploy a project interactively to any Salesforce environment.
The command first analyzes your project, active or logged-into environments, and local defaults to determine what to
deploy and where. The command then prompts you for information about this particular deployment and provides
intelligent choices based on its analysis.
For example, if your local project contains a package directory with metadata source files, the command asks if you
want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want to
deploy to. If the command finds Apex tests, it asks if you want to run them and at which level.
Similarly, if the command finds a local functions directory, the command prompts if you want to deploy it and to which
compute environment. The command prompts and connects you to a compute environment of your choice if you’re not
currently connected to any.
This command must be run from within a project.
The command stores your responses in a local file and uses them as defaults when you rerun the command. Specify
--interactive to force the command to reprompt.
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific
commands, such as "sf project deploy org", that provide additional flags.
EXAMPLES
$ sf project deploy
```

## `sf project deploy org`

You must run this command from wihin a project.

```
USAGE
$ sf project deploy org [--json] [-m <value>] [-x <value>] [-d <value>] [--target-org <value>] [-l
NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg] [--wait <value>]
FLAGS
-d, --deploy-dir=<value>... Root of local directory tree of files to deploy.
-l, --test-level=<option> [default: NoTestRun] Deployment Apex testing level.
<options: NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg>
-m, --metadata=<value>... List of metadata component names to deploy.
-x, --manifest=<value> Full file path for manifest (package.xml) of components to deploy.
--target-org=<value> Username or alias of the org you want to deploy to
--wait=<value> [default: 33] Number of minutes to wait for command to complete.
GLOBAL FLAGS
--json format output as json
DESCRIPTION
Deploy source to an org.
You must run this command from wihin a project.
The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your
source with the versions in your org.
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
Deploy the source files in a directory:
$ sf project deploy org --deploy-dir path/to/source
Deploy a specific Apex class and the objects whose source is in a directory:
$ sf project deploy org --deploy-dir "path/to/apex/classes/MyClass.cls,path/to/source/objects"
Deploy source files in a comma-separated list that contains spaces:
$ sf project deploy org --deploy-dir "path/to/objects/MyCustomObject/fields/MyField.field-meta.xml, \
path/to/apex/classes"
Deploy all Apex classes:
$ sf project deploy org --metadata ApexClass
Deploy a specific Apex class:
$ sf project deploy org --metadata ApexClass:MyApexClass
Deploy all custom objects and Apex classes:
$ sf project deploy org --metadata "CustomObject,ApexClass"
Deploy all Apex classes and two specific profiles (one of which has a space in its name):
$ sf project deploy org --metadata "ApexClass, Profile:My Profile, Profile: AnotherProfile"
Deploy all components listed in a manifest:
$ sf project deploy org --manifest path/to/package.xml
FLAG DESCRIPTIONS
-d, --deploy-dir=<value>... Root of local directory tree of files to deploy.
Root of local directory tree of files to deploy.
-l, --test-level=NoTestRun|RunSpecifiedTests|RunLocalTests|RunAllTestsInOrg Deployment Apex testing level.
Deployment Apex testing level.
-m, --metadata=<value>... List of metadata component names to deploy.
List of metadata component names to deploy.
-x, --manifest=<value> Full file path for manifest (package.xml) of components to deploy.
Full file path for manifest (package.xml) of components to deploy.
--wait=<value> Number of minutes to wait for command to complete.
Default is 33 minutes.
```

## `sf project retrieve org`
## `sf retrieve metadata`

The source you retrieve overwrites the corresponding source files in your local project . This command doesn’t attempt to merge the source from your org with your local source files. If the command detects a conflict, it displays the conflicts but doesn’t complete the process. After reviewing the conflict, rerun the command with the --force-overwrite flag to overwrite your local files.

```
USAGE
$ sf project retrieve org [--json] [-a <value>] [-n <value>] [-d <value> | [-x <value> | -m <value> | ] | ] [-t <value>]
[-w <value>]
$ sf retrieve metadata [--json] [-a <value>] [-x <value> | -m <value> | -d <value>] [-n <value>] [-t <value>] [-w
<value>]
FLAGS
-a, --api-version=<value> target API version for the retrieve
Expand Down
4 changes: 2 additions & 2 deletions package.json
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@salesforce/cli",
"description": "The Salesforce CLI",
"version": "0.0.22",
"version": "0.0.23",
"author": "Salesforce",
"bin": {
"sf": "./bin/run"
Expand Down Expand Up @@ -66,7 +66,7 @@
"@oclif/plugin-plugins": "^1.10.1",
"@sf/env": "npm:@salesforce/[email protected]",
"@sf/login": "npm:@salesforce/[email protected]",
"@sf/deploy-retrieve": "npm:@salesforce/[email protected].7",
"@sf/deploy-retrieve": "npm:@salesforce/[email protected].8",
"@sf/dr-metadata": "npm:@salesforce/[email protected]",
"@sf/telemetry": "npm:@salesforce/[email protected]",
"tslib": "^2.3.0"
Expand Down
20 changes: 5 additions & 15 deletions yarn.lock
View file
Original file line number Diff line number Diff line change
Expand Up @@ -857,16 +857,6 @@
"@salesforce/ts-types" "^1.5.20"
tslib "^2.2.0"

"@salesforce/plugin-deploy-retrieve-utils@^0.0.8":
version "0.0.8"
resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve-utils/-/plugin-deploy-retrieve-utils-0.0.8.tgz#866ba43f02f011f6501377240d13da48788edf4b"
integrity sha512-QyjjcqP4P73azL9VwxLhO/9vS3aoBTVqk77gN+gMkp3mlFksbLZYyQqRxSuoF1m5NqIf9Wu0ARGMfoSuEN9kZw==
dependencies:
"@salesforce/kit" "^1.5.8"
"@salesforce/ts-types" "^1.5.13"
cli-ux "^5.6.2"
inquirer "^8.1.1"

"@salesforce/plugin-deploy-retrieve-utils@^0.0.9":
version "0.0.9"
resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve-utils/-/plugin-deploy-retrieve-utils-0.0.9.tgz#b663d8f2653ce5ee0f37c34ea3dcd226c4daba36"
Expand Down Expand Up @@ -950,14 +940,14 @@
dependencies:
tslib "^2.2.0"

"@sf/deploy-retrieve@npm:@salesforce/[email protected].7":
version "0.0.7"
resolved "https://registry.npmjs.org/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-0.0.7.tgz#ca163531d65cfb49852e78e6e8e8bc5e60391743"
integrity sha512-Lg1Bwq0Uq1PB1U86kKxQSqqtlVz+TBc4mC+b0loymq7DTSUJks/BqA1Ibat4XiOmM0CZM+dk7Mluv3tvCtqp9w==
"@sf/deploy-retrieve@npm:@salesforce/[email protected].8":
version "0.0.8"
resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve/-/plugin-deploy-retrieve-0.0.8.tgz#8ed89b11e290c9f2770b9050a8d135d670183f13"
integrity sha512-jFrAHyG43wcFVKoBui/oWPMC7d41yU/ygHJ1hqprvsPCFw2H4ZzD77pnQTLkIJJj+KJv/3mYvG+aC38sYKfbAw==
dependencies:
"@oclif/core" "^0.5.21"
"@salesforce/core" "^3.1.1-v3.1"
"@salesforce/plugin-deploy-retrieve-utils" "^0.0.8"
"@salesforce/plugin-deploy-retrieve-utils" "^0.0.9"
tslib "^2"

"@sf/dr-metadata@npm:@salesforce/[email protected]":
Expand Down

0 comments on commit 50fecbd

Please sign in to comment.