@simplysf/simply 6.12.1 → 7.0.0

package/README.md

@@ -2546,7 +2546,7 @@ FLAG DESCRIPTIONS
     The path to write the generated HTML report to.
 ```
 
-_See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.6.1/packages/simply-permissions/lib/commands/simply/permissions/analyze.js)_
+_See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@2.0.0/packages/simply-permissions/lib/commands/simply/permissions/analyze.js)_
 
 ## `sf simply permissions assignment delete`
 
@@ -2589,7 +2589,7 @@ EXAMPLES
   $ sf simply permissions assignment delete --permission-set-group-name My_Permission_Set_Group --target-org myOrg
 ```
 
-_See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.6.1/packages/simply-permissions/lib/commands/simply/permissions/assignment/delete.js)_
+_See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@2.0.0/packages/simply-permissions/lib/commands/simply/permissions/assignment/delete.js)_
 
 ## `sf simply permissions build`
 
@@ -2597,14 +2597,13 @@ Generate permission sets from Salesforce source metadata.
 
 ```
 USAGE
-  $ sf simply permissions build [--json] [--flags-dir <value>] [-f <value> | --type read-only|view-all|modify-all | -n <value>
-    | -d <value> | --output <value> | -c <value> | --include-record-types | --label <value> | --description <value>]
+  $ sf simply permissions build [--json] [--flags-dir <value>] [--type read-only|view-all|modify-all] [-n <value>] [-d
+    <value>] [-c <value>] [--output <value>] [--include-record-types] [--label <value>] [--description <value>]
     [--check]
 
 FLAGS
   -c, --config=<value>        Path to a permission set configuration file
   -d, --directory=<value>     Path to the Salesforce project directory
-  -f, --file=<value>          Path to a permission sets file declaring every permission set to generate
   -n, --name=<value>          API name for the permission set
       --check                 Check that the generated permission sets are up to date, without writing them
       --description=<value>   Description for the permission set
@@ -2626,38 +2625,29 @@ DESCRIPTION
   override individual object, field, tab, record type, and user permission settings, as well as whether the permission
   set requires activation.
 
-  To regenerate every permission set in a project with one command, declare them all in a JSON file and pass it with
-  --file instead of the other flags. Each entry in the file's "permissionSets" array takes the same settings as one run
-  of this command; a top-level "defaults" object supplies the "directory", "output", and "includeRecordTypes" values
-  shared by every entry, and any entry can override them. An entry's "config" is either a path to a --config file or the
-  same overrides inline. Relative paths are resolved against the current directory, as they are for flags. The whole
-  file, including referenced override files and source directories, is validated before anything is written, and each
-  source directory is scanned only once. Name the file with the .psbuild.json suffix (for example
-  config/app.psbuild.json): that's how `sf simply cicd build check-permission-sets` finds permission sets files, and
-  this command warns about a file without it.
+  To regenerate every permission set in a project with one command, define each one in its own permission set build
+  file: a JSON file whose name ends in .psbuild.json (for example config/app-admin.psbuild.json), with the same settings
+  as one run of this command. "name", "type", "directory", and "output" are required; "label", "description",
+  "includeRecordTypes", and "config" are optional. "config" is either a path to a --config file or the same overrides
+  inline. Relative paths are resolved against the current directory, as they are for flags.
 
-  {
-  "defaults": {
-  "directory": "force-app",
-  "output": "force-app/main/default/permissionsets"
-  },
-  "permissionSets": [
-  { "name": "App_Read_Only", "type": "read-only" },
   {
   "name": "App_Admin",
   "type": "modify-all",
   "label": "App Admin",
+  "directory": "force-app",
+  "output": "force-app/main/default/permissionsets",
   "includeRecordTypes": true,
   "config": "config/app-admin-overrides.json"
-  },
-  {
-  "name": "App_Support",
-  "type": "view-all",
-  "config": { "userPermissions": { "ViewSetup": true } }
-  }
-  ]
   }
 
+  Then run the command with none of the flags that describe a single permission set. It builds the permission set
+  defined by every .psbuild.json file under the current directory, skipping node_modules, .git, .sf, and .sfdx. Every
+  file, including referenced override files and source directories, is validated before anything is written, no two
+  files can define the same permission set name, and each source directory is scanned only once. The results table shows
+  which file defined each permission set. If no .psbuild.json files are found, the command prints a warning and exits
+  successfully. `sf simply cicd build check-permission-sets` finds the same files.
+
   To check in CI that the committed permission sets still match their source metadata, add --check. It builds each
   permission set as usual but writes nothing: it compares each one with the file already at its output path and reports
   it as "up-to-date", "drifted", or "missing". If any permission set has drifted or is missing, the command exits with
@@ -2669,13 +2659,13 @@ EXAMPLES
 
   $ sf simply permissions build --type modify-all --name My_Admin_Access --directory force-app --config config/permission-overrides.json --output force-app/main/default/permissionsets --include-record-types
 
-  Regenerate every permission set declared in a permission sets file:
+  Regenerate the permission set defined by every .psbuild.json file under the current directory:
 
-    $ sf simply permissions build --file config/app.psbuild.json
+    $ sf simply permissions build
 
-  In CI, fail if any permission set declared in a permission sets file needs to be regenerated:
+  In CI, fail if any permission set defined by a .psbuild.json file needs to be regenerated, without writing anything:
 
-    $ sf simply permissions build --file config/app.psbuild.json --check
+    $ sf simply permissions build --check
 
 FLAG DESCRIPTIONS
   -c, --config=<value>  Path to a permission set configuration file
@@ -2685,26 +2675,19 @@ FLAG DESCRIPTIONS
 
   -d, --directory=<value>  Path to the Salesforce project directory
 
-    The path to the Salesforce source directory to scan for custom objects, fields, tabs, and record types. Required
-    unless --file is used.
-
-  -f, --file=<value>  Path to a permission sets file declaring every permission set to generate
-
-    The path to a JSON file with a "permissionSets" array, each entry describing one permission set to generate ("name",
-    "type", and optionally "label", "description", "directory", "output", "includeRecordTypes", "config"), and an
-    optional "defaults" object. Name it with the .psbuild.json suffix; any other name works but prints a warning. Can't
-    be combined with the flags that describe a single permission set.
+    The path to the Salesforce source directory to scan for custom objects, fields, tabs, and record types. Required to
+    build a single permission set.
 
   -n, --name=<value>  API name for the permission set
 
-    The API name for the generated permission set; also used to derive the output filename. Required unless --file is
-    used.
+    The API name for the generated permission set; also used to derive the output filename. Required to build a single
+    permission set.
 
   --check  Check that the generated permission sets are up to date, without writing them
 
     Instead of writing each permission set, compare what would be generated with the file already at its output path.
-    Exits with code 1 if any permission set has drifted or is missing. Works with --file and with the
-    single-permission-set flags.
+    Exits with code 1 if any permission set has drifted or is missing. Works with the single-permission-set flags, and
+    without them, which checks the permission set defined by every .psbuild.json file under the current directory.
 
   --include-record-types  Include record type visibilities
 
@@ -2712,16 +2695,16 @@ FLAG DESCRIPTIONS
 
   --output=<value>  Output directory
 
-    The directory to write the generated permission set XML file to. Required unless --file is used.
+    The directory to write the generated permission set XML file to. Required to build a single permission set.
 
   --type=read-only|view-all|modify-all  Baseline permission type
 
     The baseline permission level to generate: 'read-only' grants read access to all discovered objects and fields,
     'view-all' additionally grants view-all-records, and 'modify-all' grants full CRUD and modify-all-records access.
-    Required unless --file is used.
+    Required to build a single permission set.
 ```
 
-_See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@1.6.1/packages/simply-permissions/lib/commands/simply/permissions/build.js)_
+_See code: [@simplysf/simply-permissions](https://github.com/SimplySF/simply-plugins/blob/@simplysf/simply-permissions@2.0.0/packages/simply-permissions/lib/commands/simply/permissions/build.js)_
 
 ## `sf simply project update api-version`
 

package/oclif.manifest.json

@@ -1,4 +1,4 @@
 {
   "commands": {},
-  "version": "6.12.1"
+  "version": "7.0.0"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@simplysf/simply",
   "description": "Salesforce CLI Plugins created by @SimplySF",
-  "version": "6.12.1",
+  "version": "7.0.0",
   "author": "@ClayChipps",
   "homepage": "https://github.com/SimplySF/simply-plugins",
   "bugs": "https://github.com/SimplySF/simply-plugins/issues",
@@ -83,7 +83,7 @@
     "@simplysf/simply-document": "^0.4.13",
     "@simplysf/simply-flow": "^0.4.16",
     "@simplysf/simply-package": "^3.1.7",
-    "@simplysf/simply-permissions": "^1.6.1",
+    "@simplysf/simply-permissions": "^2.0.0",
     "@simplysf/simply-project": "^1.2.29",
     "@simplysf/simply-schema": "^0.3.34",
     "@simplysf/simply-settings": "^0.3.2",
@@ -180,5 +180,5 @@
       "output": []
     }
   },
-  "gitHead": "c2506412e12bc1025c8a9fcdc9ae26a06b64269d"
+  "gitHead": "c6b42eec62005e590b6eb019df0d317c4e200e62"
 }