@simplysf/simply 6.12.0 → 6.13.0

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
@@ -2546,7 +2546,7 @@ FLAG DESCRIPTIONS
2546
2546
  The path to write the generated HTML report to.
2547
2547
  ```
2548
2548
 
2549
- _See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.6.0/packages/simply-permissions/lib/commands/simply/permissions/analyze.js)_
2549
+ _See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.7.0/packages/simply-permissions/lib/commands/simply/permissions/analyze.js)_
2550
2550
 
2551
2551
  ## `sf simply permissions assignment delete`
2552
2552
 
@@ -2589,7 +2589,7 @@ EXAMPLES
2589
2589
  $ sf simply permissions assignment delete --permission-set-group-name My_Permission_Set_Group --target-org myOrg
2590
2590
  ```
2591
2591
 
2592
- _See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.6.0/packages/simply-permissions/lib/commands/simply/permissions/assignment/delete.js)_
2592
+ _See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.7.0/packages/simply-permissions/lib/commands/simply/permissions/assignment/delete.js)_
2593
2593
 
2594
2594
  ## `sf simply permissions build`
2595
2595
 
@@ -2636,6 +2636,12 @@ DESCRIPTION
2636
2636
  config/app.psbuild.json): that's how `sf simply cicd build check-permission-sets` finds permission sets files, and
2637
2637
  this command warns about a file without it.
2638
2638
 
2639
+ Run the command with neither --file nor any of the flags that describe a single permission set to build every
2640
+ permission sets file under the current directory: every file whose name ends in .psbuild.json, skipping node_modules,
2641
+ .git, .sf, and .sfdx. Every file is validated before anything is written, and the results table shows which file
2642
+ declared each permission set. If no permission sets files are found, the command prints a warning and exits
2643
+ successfully.
2644
+
2639
2645
  {
2640
2646
  "defaults": {
2641
2647
  "directory": "force-app",
@@ -2677,6 +2683,14 @@ EXAMPLES
2677
2683
 
2678
2684
  $ sf simply permissions build --file config/app.psbuild.json --check
2679
2685
 
2686
+ Regenerate every permission set declared in any .psbuild.json file under the current directory:
2687
+
2688
+ $ sf simply permissions build
2689
+
2690
+ Check every permission set declared in any .psbuild.json file under the current directory, without writing anything:
2691
+
2692
+ $ sf simply permissions build --check
2693
+
2680
2694
  FLAG DESCRIPTIONS
2681
2695
  -c, --config=<value> Path to a permission set configuration file
2682
2696
 
@@ -2685,26 +2699,27 @@ FLAG DESCRIPTIONS
2685
2699
 
2686
2700
  -d, --directory=<value> Path to the Salesforce project directory
2687
2701
 
2688
- The path to the Salesforce source directory to scan for custom objects, fields, tabs, and record types. Required
2689
- unless --file is used.
2702
+ The path to the Salesforce source directory to scan for custom objects, fields, tabs, and record types. Required to
2703
+ build a single permission set.
2690
2704
 
2691
2705
  -f, --file=<value> Path to a permission sets file declaring every permission set to generate
2692
2706
 
2693
2707
  The path to a JSON file with a "permissionSets" array, each entry describing one permission set to generate ("name",
2694
2708
  "type", and optionally "label", "description", "directory", "output", "includeRecordTypes", "config"), and an
2695
2709
  optional "defaults" object. Name it with the .psbuild.json suffix; any other name works but prints a warning. Can't
2696
- be combined with the flags that describe a single permission set.
2710
+ be combined with the flags that describe a single permission set. If you omit --file and those flags, every
2711
+ .psbuild.json file under the current directory is built.
2697
2712
 
2698
2713
  -n, --name=<value> API name for the permission set
2699
2714
 
2700
- The API name for the generated permission set; also used to derive the output filename. Required unless --file is
2701
- used.
2715
+ The API name for the generated permission set; also used to derive the output filename. Required to build a single
2716
+ permission set.
2702
2717
 
2703
2718
  --check Check that the generated permission sets are up to date, without writing them
2704
2719
 
2705
2720
  Instead of writing each permission set, compare what would be generated with the file already at its output path.
2706
- Exits with code 1 if any permission set has drifted or is missing. Works with --file and with the
2707
- single-permission-set flags.
2721
+ Exits with code 1 if any permission set has drifted or is missing. Works with --file, with the single-permission-set
2722
+ flags, and with neither, which checks every .psbuild.json file under the current directory.
2708
2723
 
2709
2724
  --include-record-types Include record type visibilities
2710
2725
 
@@ -2712,16 +2727,16 @@ FLAG DESCRIPTIONS
2712
2727
 
2713
2728
  --output=<value> Output directory
2714
2729
 
2715
- The directory to write the generated permission set XML file to. Required unless --file is used.
2730
+ The directory to write the generated permission set XML file to. Required to build a single permission set.
2716
2731
 
2717
2732
  --type=read-only|view-all|modify-all Baseline permission type
2718
2733
 
2719
2734
  The baseline permission level to generate: 'read-only' grants read access to all discovered objects and fields,
2720
2735
  'view-all' additionally grants view-all-records, and 'modify-all' grants full CRUD and modify-all-records access.
2721
- Required unless --file is used.
2736
+ Required to build a single permission set.
2722
2737
  ```
2723
2738
 
2724
- _See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.6.0/packages/simply-permissions/lib/commands/simply/permissions/build.js)_
2739
+ _See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.7.0/packages/simply-permissions/lib/commands/simply/permissions/build.js)_
2725
2740
 
2726
2741
  ## `sf simply project update api-version`
2727
2742
 
@@ -1,4 +1,4 @@
1
1
  {
2
2
  "commands": {},
3
- "version": "6.12.0"
3
+ "version": "6.13.0"
4
4
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@simplysf/simply",
3
3
  "description": "Salesforce CLI Plugins created by @SimplySF",
4
- "version": "6.12.0",
4
+ "version": "6.13.0",
5
5
  "author": "@ClayChipps",
6
6
  "homepage": "https://github.com/SimplySF/simply-plugins",
7
7
  "bugs": "https://github.com/SimplySF/simply-plugins/issues",
@@ -83,7 +83,7 @@
83
83
  "@simplysf/simply-document": "^0.4.13",
84
84
  "@simplysf/simply-flow": "^0.4.16",
85
85
  "@simplysf/simply-package": "^3.1.7",
86
- "@simplysf/simply-permissions": "^1.6.0",
86
+ "@simplysf/simply-permissions": "^1.7.0",
87
87
  "@simplysf/simply-project": "^1.2.29",
88
88
  "@simplysf/simply-schema": "^0.3.34",
89
89
  "@simplysf/simply-settings": "^0.3.2",
@@ -180,5 +180,5 @@
180
180
  "output": []
181
181
  }
182
182
  },
183
- "gitHead": "cfc320bc665f61d2ab5c702ea9120bddc34b6078"
183
+ "gitHead": "970835763c6ff199a1a853eec344807f35e3315c"
184
184
  }