Skip to content

Commit

Permalink
chore(release): 0.0.28 [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
SF-CLI-BOT committed Jul 27, 2021
1 parent 9e80363 commit 6fab6ba
Show file tree
Hide file tree
Showing 4 changed files with 62 additions and 42 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

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.28](https://github.com/salesforcecli/cli/compare/v0.0.27...v0.0.28) (2021-07-27)

### [0.0.27](https://github.com/salesforcecli/cli/compare/v0.0.26...v0.0.27) (2021-07-26)

### [0.0.26](https://github.com/salesforcecli/cli/compare/v0.0.25...v0.0.26) (2021-07-22)
Expand Down
78 changes: 48 additions & 30 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ $ npm install -g @salesforce/cli
$ sf COMMAND
running command...
$ sf (-v|--version|version)
@salesforce/cli/0.0.27 linux-x64 node-v14.17.3
@salesforce/cli/0.0.28 linux-x64 node-v14.17.3
$ sf --help [COMMAND]
USAGE
$ sf COMMAND
Expand Down Expand Up @@ -63,10 +63,14 @@ USAGE
$ sf config get [--json] [--verbose]
FLAGS
--json format output as json
--verbose
--verbose Display whether the configuration variables are set locally or globally.
GLOBAL FLAGS
--json format output as json
DESCRIPTION
Get the value of a configuration variable.
Run "sf config list" to see all the configuration variables you've set. Global configuration variable are always
displayed; local ones are displayed if you run the command in a project directory.
Expand All @@ -88,10 +92,12 @@ Global configuration variables apply to any directory and are always displayed.
USAGE
$ sf config list [--json]
FLAGS
GLOBAL FLAGS
--json format output as json
DESCRIPTION
List the configuration variables that you've previously set.
Global configuration variables apply to any directory and are always displayed. If you run this command from a project
directory, local configuration variables are also displayed.
Expand All @@ -110,10 +116,14 @@ USAGE
$ sf config set [--json] [-g]
FLAGS
-g, --global
--json format output as json
-g, --global Set the configuration variables globally, so they can be used from any directory.
GLOBAL FLAGS
--json format output as json
DESCRIPTION
Set one or more configuration variables, such as your default environment.
Use configuration variables to set CLI defaults, such as your default environment or the API version you want the CLI
to use. For example, if you set the "target-org" configuration variable, you don't need to specify it as a "sf deploy
metadata" flag if you're deploying to your default org.
Expand Down Expand Up @@ -158,10 +168,14 @@ USAGE
$ sf config unset [--json] [-g]
FLAGS
-g, --global
--json format output as json
-g, --global Unset the configuration variables globally, so they can no longer be used from any directory.
GLOBAL FLAGS
--json format output as json
DESCRIPTION
Unset local or global configuration variables.
Local configuration variables apply only to your current project. Global configuration variables apply in any
directory.
Expand Down Expand Up @@ -376,7 +390,7 @@ EXAMPLES

## `sf env list`

By default, the command displays only active environments. For orgs, active means unexpired scratch orgs and orgs you’re currently logged into. For compute environments, active means the environments connected to orgs you’re currently logged into. Use the --all flag to list expired or deleted scratch orgs and compute environments that aren’t connected to logged-in orgs. Warning: the latter list could be very long.
The command displays only active environments. For orgs, active means unexpired scratch orgs and orgs you’re currently logged into.

```
USAGE
Expand All @@ -385,55 +399,59 @@ USAGE
FLAGS
-x, --extended Show extra columns.
--columns=<value>... Only show provided columns.
--columns=<value>... List of columns to display.
--csv Output in csv format [alias: --output=csv]
--filter=<value> Filter property by partial string matching.
--no-header Hide table header from output.
--no-truncate Do not truncate output to fit screen.
--no-truncate Don't truncate output to fit screen.
--output=<option> Output in a more machine friendly format.
--output=<option> Format in which to display the output.
<options: csv|json|yaml>
--sort=<value> Property to sort by (prepend '-' for descending).
--sort=<value> Column to sort by (prepend '-' for descending).
GLOBAL FLAGS
--json format output as json
DESCRIPTION
List the environments you’ve created or logged into.
By default, the command displays only active environments. For orgs, active means unexpired scratch orgs and orgs
you’re currently logged into. For compute environments, active means the environments connected to orgs you’re
currently logged into. Use the --all flag to list expired or deleted scratch orgs and compute environments that aren’t
connected to logged-in orgs. Warning: the latter list could be very long.
The command displays only active environments. For orgs, active means unexpired scratch orgs and orgs you’re currently
logged into.
Output is displayed in multiple tables, one for each environment type. For example, the Salesforce Orgs table lists
the non-scratch orgs you’re logged into, such as sandboxes, Dev Hubs, production orgs, and so on. Scratch orgs and
compute environments get their own tables.
the non-scratch orgs you’re logged into, such as sandboxes, Dev Hubs, production orgs, and so on. Scratch orgs get
their own table.
For non-scratch orgs, the Username column refers to the user you logged into the org with. For scratch orgs it refers
to the username that was generated for you when you created the scratch org. The first column indicates the default
environment for each type.
to the username that was generated for you when you created the scratch org. The table also displays the default
environment for each type, the instance URL, and how you authorized (logged into) the org, either using a web browser
or JWT.
Use the table-manipulation flags, such as --filter and --sort, to change how the data is displayed.
Run "sf env display" to view details about a specific environment.
EXAMPLES
List all environments:
$ sf env list --all
List all active environments:
Filter the output to list only connected orgs. Rows from only the Salesforce Orgs table are displayed because it’s
the only table with a "Status" column.
$ sf env list
$ sf env list --filter "Status=Connected"
Filter the output to list only orgs you authorized using a web browser; "OAuth Method" is the name of a column:
List only scratch orgs that expire after May 30, 2021:
$ sf env list --filter "Expiration>2021-05-30"
$ sf env list --filter "OAuth Method=web"
Display only the Alias column and sort the aliases in descending order:
$ sf env list --sort "-Alias" --columns "Alias"
Don't truncate the displayed output:
$ sf env list --no-truncate
Display only the table data, not the headers, in comma-separated value (csv) format:
$ sf env list --csv --no-header
```

## `sf env open`
Expand Down
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,8 @@
"@oclif/plugin-plugins": "^1.10.1",
"@sf/config": "npm:@salesforce/[email protected]",
"@sf/deploy-retrieve": "npm:@salesforce/[email protected]",
"@sf/dr-metadata": "npm:@salesforce/[email protected].8",
"@sf/env": "npm:@salesforce/[email protected].13",
"@sf/dr-metadata": "npm:@salesforce/[email protected].9",
"@sf/env": "npm:@salesforce/[email protected].14",
"@sf/login": "npm:@salesforce/[email protected]",
"@sf/telemetry": "npm:@salesforce/[email protected]",
"tslib": "^2.3.0"
Expand Down
20 changes: 10 additions & 10 deletions yarn.lock
Original file line number Diff line number Diff line change
Expand Up @@ -1114,23 +1114,23 @@
"@salesforce/plugin-deploy-retrieve-utils" "^0.0.9"
tslib "^2"

"@sf/dr-metadata@npm:@salesforce/[email protected].8":
version "0.0.8"
resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve-metadata/-/plugin-deploy-retrieve-metadata-0.0.8.tgz#b6fba8103862d99feea89c65579b7fe362ce93ed"
integrity sha512-tAC+W+ahyqhSMYv2Y1ciLvwk4ZF9XuDjsosVONSDdtvbJtz/DkeMhafGgP3mG4Ut7qk/3IKHLUvCaDc57SpuQQ==
"@sf/dr-metadata@npm:@salesforce/[email protected].9":
version "0.0.9"
resolved "https://registry.yarnpkg.com/@salesforce/plugin-deploy-retrieve-metadata/-/plugin-deploy-retrieve-metadata-0.0.9.tgz#57ba5dacaa38add734f37c70a10fbb820c4d7b47"
integrity sha512-QFKMsyWr5BJRk3EQLZJEWKozQkW5OPnOQOq97NV2MUkztiL1LfTqpy3PBammQPXisvLzBHLrrg8Vp+/0Yku1HQ==
dependencies:
"@oclif/core" "^0.5.21"
"@salesforce/core" "^3.1.1-v3.2"
"@oclif/core" "^0.5.26"
"@salesforce/core" "^3.3.4"
"@salesforce/plugin-deploy-retrieve-utils" "^0.0.9"
"@salesforce/source-deploy-retrieve" "^3.1.1"
chalk "^4.1.1"
cli-ux "^5.5.1"
tslib "^2"

"@sf/env@npm:@salesforce/[email protected].13":
version "0.0.13"
resolved "https://registry.yarnpkg.com/@salesforce/plugin-env/-/plugin-env-0.0.13.tgz#e15e4ef1cb4312652c88b43c74fc8f8c8589112d"
integrity sha512-6K8DMLMXTs22XPWiaMyouL145yId2zB/BE/CrntMcVbd+X7RRZ7QpzF2OVCGAbTnpdS6vaM7y11aS6GkETG1yQ==
"@sf/env@npm:@salesforce/[email protected].14":
version "0.0.14"
resolved "https://registry.yarnpkg.com/@salesforce/plugin-env/-/plugin-env-0.0.14.tgz#a597f6e754e0e18ddfd57196bff8ecb752417e40"
integrity sha512-YVZ4MZG7//1Ei/I5ktDmjKRZXwblK2+2UZRMZutbBDMTweVffBYzNB2BcLEHUd3Dd3tSOmLhAb/l1zCn287APA==
dependencies:
"@oclif/core" "^0.5.21"
"@salesforce/core" v3-beta
Expand Down

0 comments on commit 6fab6ba

Please sign in to comment.