@salesforce/plugin-settings 1.4.33 → 1.4.34

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.
package/README.md CHANGED
@@ -107,7 +107,7 @@ EXAMPLES
107
107
  $ sf alias list
108
108
  ```
109
109
 
110
- _See code: [src/commands/alias/list.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/alias/list.ts)_
110
+ _See code: [src/commands/alias/list.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/alias/list.ts)_
111
111
 
112
112
  ## `sf alias set`
113
113
 
@@ -155,7 +155,7 @@ EXAMPLES
155
155
  $ sf alias set my-scratch-org test-ss0xut7txzxf@example.com
156
156
  ```
157
157
 
158
- _See code: [src/commands/alias/set.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/alias/set.ts)_
158
+ _See code: [src/commands/alias/set.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/alias/set.ts)_
159
159
 
160
160
  ## `sf alias unset`
161
161
 
@@ -194,7 +194,7 @@ EXAMPLES
194
194
  $ sf alias unset --all [--no-prompt]
195
195
  ```
196
196
 
197
- _See code: [src/commands/alias/unset.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/alias/unset.ts)_
197
+ _See code: [src/commands/alias/unset.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/alias/unset.ts)_
198
198
 
199
199
  ## `sf config get`
200
200
 
@@ -213,11 +213,9 @@ GLOBAL FLAGS
213
213
  DESCRIPTION
214
214
  Get the value of a configuration variable.
215
215
 
216
- Run "sf config list" to see all the configuration variables you've set. Global configuration variable are always
217
- displayed; local ones are displayed if you run the command in a project directory. Run "sf config set" to set a
218
- configuration variable.
216
+ Run "sf config list" to see the configuration variables you've already set and their level (local or global).
219
217
 
220
- For the full list of available configuration variables, see
218
+ Run "sf config set" to set a configuration variable. For the full list of available configuration variables, see
221
219
  https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
222
220
 
223
221
  ALIASES
@@ -233,7 +231,7 @@ EXAMPLES
233
231
  $ sf config get target-org api-version --verbose
234
232
  ```
235
233
 
236
- _See code: [src/commands/config/get.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/config/get.ts)_
234
+ _See code: [src/commands/config/get.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/config/get.ts)_
237
235
 
238
236
  ## `sf config list`
239
237
 
@@ -249,8 +247,16 @@ GLOBAL FLAGS
249
247
  DESCRIPTION
250
248
  List the configuration variables that you've previously set.
251
249
 
252
- Global configuration variables apply to any Salesforce DX project and are always displayed. If you run this command
253
- from a project directory, local configuration variables are also displayed.
250
+ A config variable can be global or local, depending on whether you used the --global flag when you set it. Local
251
+ config variables apply only to the current project and override global config variables, which apply to all projects.
252
+ You can set all config variables as environment variables. Environment variables override their equivalent local and
253
+ global config variables.
254
+
255
+ The output of this command takes into account your current context. For example, let's say you run this command from a
256
+ Salesforce DX project in which you've locally set the "target-org" config variable. The command displays the local
257
+ value, even if you've also set "target-org" globally. If you haven't set the config variable locally, then the global
258
+ value is displayed, if set. If you set the SF_TARGET_ORG environment variable, it's displayed as such and overrides
259
+ any locally or globally set "target-org" config variable.
254
260
 
255
261
  For the full list of available configuration variables, see
256
262
  https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
@@ -259,12 +265,12 @@ ALIASES
259
265
  $ sf force config list
260
266
 
261
267
  EXAMPLES
262
- List both global configuration variables and those local to your project:
268
+ List the global and local configuration variables that apply to your current context:
263
269
 
264
270
  $ sf config list
265
271
  ```
266
272
 
267
- _See code: [src/commands/config/list.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/config/list.ts)_
273
+ _See code: [src/commands/config/list.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/config/list.ts)_
268
274
 
269
275
  ## `sf config set`
270
276
 
@@ -298,6 +304,9 @@ DESCRIPTION
298
304
 
299
305
  Run "sf config list" to see the configuration variables you've already set and their level (local or global).
300
306
 
307
+ If you're setting a single config variable, you don't need to use an equal sign between the variable and value. But
308
+ you must use the equal sign if setting multiple config variables.
309
+
301
310
  For the full list of available configuration variables, see
302
311
  https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
303
312
 
@@ -307,23 +316,18 @@ ALIASES
307
316
  EXAMPLES
308
317
  Set the local target-org configuration variable to an org username:
309
318
 
310
- $ sf config set target-org=me@my.org
319
+ $ sf config set target-org me@my.org
311
320
 
312
321
  Set the local target-org configuration variable to an alias:
313
322
 
314
- $ sf config set target-org=my-scratch-org
315
-
316
- Set the global target-org configuration variable:
317
-
318
- $ sf config set --global target-org=my-scratch-org
323
+ $ sf config set target-org my-scratch-org
319
324
 
320
- Set a single configuration variable without using an equal sign; this syntax doesn't work when setting multiple
321
- configuration variables:
325
+ Set the global target-org and target-dev-hub configuration variables using aliases:
322
326
 
323
- $ sf config set target-org me@my.com
327
+ $ sf config set --global target-org=my-scratch-org target-dev-hub=my-dev-hub
324
328
  ```
325
329
 
326
- _See code: [src/commands/config/set.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/config/set.ts)_
330
+ _See code: [src/commands/config/set.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/config/set.ts)_
327
331
 
328
332
  ## `sf config unset`
329
333
 
@@ -334,8 +338,7 @@ USAGE
334
338
  $ sf config unset [--json] [-g]
335
339
 
336
340
  FLAGS
337
- -g, --global Unset the configuration variables globally, so they can no longer be used from any Salesforce DX
338
- project.
341
+ -g, --global Unset the configuration variables globally.
339
342
 
340
343
  GLOBAL FLAGS
341
344
  --json Format output as json.
@@ -362,6 +365,6 @@ EXAMPLES
362
365
  $ sf config unset target-org api-version --global
363
366
  ```
364
367
 
365
- _See code: [src/commands/config/unset.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.33/src/commands/config/unset.ts)_
368
+ _See code: [src/commands/config/unset.ts](https://github.com/salesforcecli/plugin-settings/blob/1.4.34/src/commands/config/unset.ts)_
366
369
 
367
370
  <!-- commandsstop -->
@@ -4,9 +4,9 @@ Get the value of a configuration variable.
4
4
 
5
5
  # description
6
6
 
7
- 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. Run "sf config set" to set a configuration variable.
7
+ Run "sf config list" to see the configuration variables you've already set and their level (local or global).
8
8
 
9
- For the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
9
+ Run "sf config set" to set a configuration variable. For the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
10
10
 
11
11
  # examples
12
12
 
@@ -4,12 +4,14 @@ List the configuration variables that you've previously set.
4
4
 
5
5
  # description
6
6
 
7
- Global configuration variables apply to any Salesforce DX project and are always displayed. If you run this command from a project directory, local configuration variables are also displayed.
7
+ A config variable can be global or local, depending on whether you used the --global flag when you set it. Local config variables apply only to the current project and override global config variables, which apply to all projects. You can set all config variables as environment variables. Environment variables override their equivalent local and global config variables.
8
+
9
+ The output of this command takes into account your current context. For example, let's say you run this command from a Salesforce DX project in which you've locally set the "target-org" config variable. The command displays the local value, even if you've also set "target-org" globally. If you haven't set the config variable locally, then the global value is displayed, if set. If you set the SF_TARGET_ORG environment variable, it's displayed as such and overrides any locally or globally set "target-org" config variable.
8
10
 
9
11
  For the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
10
12
 
11
13
  # examples
12
14
 
13
- - List both global configuration variables and those local to your project:
15
+ - List the global and local configuration variables that apply to your current context:
14
16
 
15
17
  $ <%= config.bin %> <%= command.id %>
@@ -16,25 +16,23 @@ The resolution order if you've set a flag value in multiple ways is as follows:
16
16
 
17
17
  Run "sf config list" to see the configuration variables you've already set and their level (local or global).
18
18
 
19
+ If you're setting a single config variable, you don't need to use an equal sign between the variable and value. But you must use the equal sign if setting multiple config variables.
20
+
19
21
  For the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.
20
22
 
21
23
  # examples
22
24
 
23
25
  - Set the local target-org configuration variable to an org username:
24
26
 
25
- <%= config.bin %> <%= command.id %> target-org=me@my.org
27
+ <%= config.bin %> <%= command.id %> target-org me@my.org
26
28
 
27
29
  - Set the local target-org configuration variable to an alias:
28
30
 
29
- <%= config.bin %> <%= command.id %> target-org=my-scratch-org
30
-
31
- - Set the global target-org configuration variable:
32
-
33
- <%= config.bin %> <%= command.id %> --global target-org=my-scratch-org
31
+ <%= config.bin %> <%= command.id %> target-org my-scratch-org
34
32
 
35
- - Set a single configuration variable without using an equal sign; this syntax doesn't work when setting multiple configuration variables:
33
+ - Set the global target-org and target-dev-hub configuration variables using aliases:
36
34
 
37
- <%= config.bin %> <%= command.id %> target-org me@my.com
35
+ <%= config.bin %> <%= command.id %> --global target-org=my-scratch-org target-dev-hub=my-dev-hub
38
36
 
39
37
  # flags.global.summary
40
38
 
@@ -20,7 +20,7 @@ For the full list of available configuration variables, see https://developer.sa
20
20
 
21
21
  # flags.global.summary
22
22
 
23
- Unset the configuration variables globally, so they can no longer be used from any Salesforce DX project.
23
+ Unset the configuration variables globally.
24
24
 
25
25
  # error.NoConfigKeysFound
26
26
 
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.4.33",
2
+ "version": "1.4.34",
3
3
  "commands": {
4
4
  "alias:list": {
5
5
  "id": "alias:list",
@@ -136,7 +136,7 @@
136
136
  "config:get": {
137
137
  "id": "config:get",
138
138
  "summary": "Get the value of a configuration variable.",
139
- "description": "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. Run \"sf config set\" to set a configuration variable.\n\nFor the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.",
139
+ "description": "Run \"sf config list\" to see the configuration variables you've already set and their level (local or global).\n\nRun \"sf config set\" to set a configuration variable. For the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.",
140
140
  "strict": false,
141
141
  "pluginName": "@salesforce/plugin-settings",
142
142
  "pluginAlias": "@salesforce/plugin-settings",
@@ -218,7 +218,7 @@
218
218
  "config:list": {
219
219
  "id": "config:list",
220
220
  "summary": "List the configuration variables that you've previously set.",
221
- "description": "Global configuration variables apply to any Salesforce DX project and are always displayed. If you run this command from a project directory, local configuration variables are also displayed.\n\nFor the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.",
221
+ "description": "A config variable can be global or local, depending on whether you used the --global flag when you set it. Local config variables apply only to the current project and override global config variables, which apply to all projects. You can set all config variables as environment variables. Environment variables override their equivalent local and global config variables.\n\nThe output of this command takes into account your current context. For example, let's say you run this command from a Salesforce DX project in which you've locally set the \"target-org\" config variable. The command displays the local value, even if you've also set \"target-org\" globally. If you haven't set the config variable locally, then the global value is displayed, if set. If you set the SF_TARGET_ORG environment variable, it's displayed as such and overrides any locally or globally set \"target-org\" config variable. \n\nFor the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.",
222
222
  "strict": true,
223
223
  "pluginName": "@salesforce/plugin-settings",
224
224
  "pluginAlias": "@salesforce/plugin-settings",
@@ -227,7 +227,7 @@
227
227
  "force:config:list"
228
228
  ],
229
229
  "examples": [
230
- "List both global configuration variables and those local to your project:\n$ <%= config.bin %> <%= command.id %>"
230
+ "List the global and local configuration variables that apply to your current context:\n$ <%= config.bin %> <%= command.id %>"
231
231
  ],
232
232
  "deprecateAliases": true,
233
233
  "flags": {
@@ -255,7 +255,7 @@
255
255
  "config:set": {
256
256
  "id": "config:set",
257
257
  "summary": "Set one or more configuration variables, such as your default org.",
258
- "description": "Use configuration variables to set CLI defaults, such as your default org 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.\n\nLocal configuration variables apply only to your current project. Global variables, specified with the --global flag, apply in any Salesforce DX project.\n\nThe resolution order if you've set a flag value in multiple ways is as follows:\n\n 1. Flag value specified at the command line.\n 2. Local (project-level) configuration variable.\n 3. Global configuration variable.\n\nRun \"sf config list\" to see the configuration variables you've already set and their level (local or global).\n\nFor the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.",
258
+ "description": "Use configuration variables to set CLI defaults, such as your default org 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.\n\nLocal configuration variables apply only to your current project. Global variables, specified with the --global flag, apply in any Salesforce DX project.\n\nThe resolution order if you've set a flag value in multiple ways is as follows:\n\n 1. Flag value specified at the command line.\n 2. Local (project-level) configuration variable.\n 3. Global configuration variable.\n\nRun \"sf config list\" to see the configuration variables you've already set and their level (local or global).\n\nIf you're setting a single config variable, you don't need to use an equal sign between the variable and value. But you must use the equal sign if setting multiple config variables.\n\nFor the full list of available configuration variables, see https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm.",
259
259
  "strict": false,
260
260
  "pluginName": "@salesforce/plugin-settings",
261
261
  "pluginAlias": "@salesforce/plugin-settings",
@@ -264,10 +264,9 @@
264
264
  "force:config:set"
265
265
  ],
266
266
  "examples": [
267
- "Set the local target-org configuration variable to an org username:\n<%= config.bin %> <%= command.id %> target-org=me@my.org",
268
- "Set the local target-org configuration variable to an alias:\n<%= config.bin %> <%= command.id %> target-org=my-scratch-org",
269
- "Set the global target-org configuration variable:\n<%= config.bin %> <%= command.id %> --global target-org=my-scratch-org",
270
- "Set a single configuration variable without using an equal sign; this syntax doesn't work when setting multiple configuration variables:\n<%= config.bin %> <%= command.id %> target-org me@my.com"
267
+ "Set the local target-org configuration variable to an org username:\n<%= config.bin %> <%= command.id %> target-org me@my.org",
268
+ "Set the local target-org configuration variable to an alias:\n<%= config.bin %> <%= command.id %> target-org my-scratch-org",
269
+ "Set the global target-org and target-dev-hub configuration variables using aliases:\n<%= config.bin %> <%= command.id %> --global target-org=my-scratch-org target-dev-hub=my-dev-hub"
271
270
  ],
272
271
  "deprecateAliases": true,
273
272
  "flags": {
@@ -376,7 +375,7 @@
376
375
  "name": "global",
377
376
  "type": "boolean",
378
377
  "char": "g",
379
- "summary": "Unset the configuration variables globally, so they can no longer be used from any Salesforce DX project.",
378
+ "summary": "Unset the configuration variables globally.",
380
379
  "allowNo": false,
381
380
  "deprecateAliases": true
382
381
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@salesforce/plugin-settings",
3
3
  "description": "configure the Salesforce CLI",
4
- "version": "1.4.33",
4
+ "version": "1.4.34",
5
5
  "author": "Salesforce",
6
6
  "bugs": "https://github.com/forcedotcom/cli/issues",
7
7
  "dependencies": {
@@ -14,23 +14,23 @@
14
14
  "devDependencies": {
15
15
  "@oclif/plugin-command-snapshot": "^4.0.14",
16
16
  "@oclif/test": "^2.5.6",
17
- "@salesforce/cli-plugins-testkit": "^4.4.2",
17
+ "@salesforce/cli-plugins-testkit": "^4.4.7",
18
18
  "@salesforce/dev-config": "^4.0.1",
19
- "@salesforce/dev-scripts": "^5.10.0",
19
+ "@salesforce/dev-scripts": "^5.11.0",
20
20
  "@salesforce/kit": "^3.0.11",
21
- "@salesforce/plugin-command-reference": "^3.0.36",
22
- "@salesforce/plugin-deploy-retrieve": "^1.17.11",
21
+ "@salesforce/plugin-command-reference": "^3.0.40",
22
+ "@salesforce/plugin-deploy-retrieve": "^1.18.7",
23
23
  "@salesforce/prettier-config": "^0.0.3",
24
- "@salesforce/ts-sinon": "^1.4.16",
24
+ "@salesforce/ts-sinon": "^1.4.17",
25
25
  "@salesforce/ts-types": "^2.0.6",
26
26
  "@swc/core": "^1.3.27",
27
27
  "@types/fast-levenshtein": "^0.0.2",
28
28
  "@types/fs-extra": "^9.0.13",
29
- "@types/shelljs": "^0.8.12",
29
+ "@types/shelljs": "^0.8.13",
30
30
  "@typescript-eslint/eslint-plugin": "^5.62.0",
31
31
  "@typescript-eslint/parser": "^5.62.0",
32
- "chai": "^4.3.8",
33
- "eslint": "^8.50.0",
32
+ "chai": "^4.3.10",
33
+ "eslint": "^8.51.0",
34
34
  "eslint-config-prettier": "^8.10.0",
35
35
  "eslint-config-salesforce": "^2.0.2",
36
36
  "eslint-config-salesforce-license": "^0.2.0",
@@ -38,7 +38,7 @@
38
38
  "eslint-plugin-header": "^3.1.1",
39
39
  "eslint-plugin-import": "^2.28.1",
40
40
  "eslint-plugin-jsdoc": "^43.0.5",
41
- "eslint-plugin-sf-plugin": "^1.16.0",
41
+ "eslint-plugin-sf-plugin": "^1.16.9",
42
42
  "fs-extra": "^10.1.0",
43
43
  "husky": "^7.0.4",
44
44
  "mocha": "^9.2.2",
@@ -228,7 +228,7 @@
228
228
  }
229
229
  },
230
230
  "sfdx": {
231
- "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-settings/1.4.33.crt",
232
- "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-settings/1.4.33.sig"
231
+ "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-settings/1.4.34.crt",
232
+ "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-settings/1.4.34.sig"
233
233
  }
234
234
  }