@pnp/cli-microsoft365 5.8.0-beta.bc15f2b → 5.8.0-beta.c1d5041

package/docs/docs/cmd/pp/environment/environment-list.md

@@ -10,7 +10,7 @@ m365 pp environment list [options]
 
 ## Options
 
-`-a, --asAdmin [teamId]`
+`-a, --asAdmin`
 Run the command as admin and retrieve all environments. Lists only environments you have explicitly are assigned permissions to by default.
 
 --8<-- "docs/cmd/_global.md"

package/docs/docs/cmd/request.md

@@ -0,0 +1,76 @@
+# request
+
+Executes the specified web request using CLI for Microsoft 365
+
+## Usage
+
+```sh
+m365 request [options]
+```
+
+## Options
+
+`-u, --url <url>`
+: The request URL.
+
+`-m, --method [method]`
+: The HTTP request method. Accepted values are `get, post, put, patch, delete, head, options`. The default value is `get`.
+
+`-r, --resource [resource]`
+: The resource uri for which the CLI should acquire a token from AAD in order to access
+the service.
+
+`-b, --body [body]`
+: The request body. Optionally use `@example.json` to load the body from a file.
+
+`-p, --filePath [filePath]`
+: The file path to save the response to. This option can be used when downloading files.
+
+--8<-- "docs/cmd/_global.md"
+
+## Remarks
+
+When executing a request, CLI will take care of the very basic configuration, and you'll need to specify all additional information, such as headers, method and body. CLI will take care for you of:
+
+- applying compression and handling throttling,
+- setting the `accept` to `application/json` if you don't specify it yourself,
+- setting the `authorization` header to the bearer token obtained for the resource determined from the request URL
+
+If you specify the `resource` option, the CLI will try to retrieve a valid token for the resource instead of determining the resource based on the url. The value doesn't have to be a URL. It can be also a URI like `app://<guid>`.
+
+Specify additional headers by typing them as options, for example: `--content-type "application/json"`, `--if-match "*"`, `--x-requestdigest "somedigest"`.
+
+!!! important
+    When building the request, depending on the shell you use, you might need to escape all `$` characters in the URL, request headers, and the body. If you don't do it, the shell will treat it as a variable and will remove the following word from the request, breaking the request.
+
+## Examples
+
+Call the SharePoint Rest API using a GET request with a constructed URL containing expands, filters and selects.
+
+```sh
+m365 request --url "https://contoso.sharepoint.com/sites/project-x/_api/web/siteusers?\$filter=IsShareByEmailGuestUser eq true&\$expand=Groups&\$select=Title,LoginName,Email,Groups/LoginName" --accept "application/json;odata=nometadata"
+```
+
+Call the Microsoft Graph beta endpoint using a GET request.
+
+```sh
+m365 request --url "https://graph.microsoft.com/beta/me"
+```
+
+Call the SharePoint API to retrieve a form digest.
+
+```sh
+m365 request --method post --url "https://contoso.sharepoint.com/sites/project-x/_api/contextinfo"
+```
+
+Call the SharePoint API to update a site title.
+
+```sh
+m365 request --method post --url "https://contoso.sharepoint.com/sites/project-x/_api/web" --body '{ "Title": "New title" }' --content-type "application/json" --x-http-method "PATCH"
+```
+
+Call the Microsoft Graph to get a profile photo.
+
+```sh
+m365 request --url "https://graph.microsoft.com/beta/me/photo/\$value" --filePath ./profile-pic.jpg
+```

package/docs/docs/cmd/spfx/spfx-doctor.md

@@ -37,7 +37,7 @@ This commands helps you to verify if your environment meets all prerequisites fo
 
 The command starts by detecting the version of SharePoint Framework that you want to use. First, it looks at the current project. If you didn't run the command in the context of a SharePoint Framework project, the command will try to determine the SharePoint Framework version based on the SharePoint Framework Yeoman generator that you have installed either in the current directory or globally.
 
-Based on the determined version of the SharePoint Framework, the command will look at other dependencies such as Node.js, npm, Yeoman, Gulp and TypeScript to verify if their meet the requirements of that particular version of the SharePoint Framework.
+Based on the determined version of the SharePoint Framework, the command will look at other dependencies such as Node.js, npm, Yeoman, Gulp CLI and TypeScript to verify if their meet the requirements of that particular version of the SharePoint Framework.
 
 If you miss any required tools or use a version that doesn't meet the SharePoint Framework requirements, the command will give you a list of recommendation how to address these issues.
 
@@ -51,11 +51,11 @@ Next to verifying the readiness of your environment to use a particular version
 Verify if your environment meets the requirements to work with the SharePoint Framework
 
 ```sh
-m365 spfx doctor
+m365 spfx doctor --output text
 ```
 
 Verify if your environment meets the requirements to work with the SharePoint Framework and also if the version of the SharePoint Framework that you're using is compatible with SharePoint 2019
 
 ```sh
-m365 spfx doctor --env sp2019
+m365 spfx doctor --env sp2019 --output text
 ```

package/docs/docs/cmd/spo/contenttype/contenttype-set.md

@@ -0,0 +1,45 @@
+# spo contenttype set
+
+Update existing content type
+
+## Usage
+
+```sh
+m365 spo contenttype set [options]
+```
+
+## Options
+
+`-u, --webUrl <webUrl>`
+: URL of the site where the content type to update is defined.
+
+`-i, --id [id]`
+: ID of the content type to update. Specify `id` or `name` but not both, one is required.
+
+`-n, name [name]`
+: Name of the content type to update. Specify the `id` or the `name` but not both, one is required.
+
+`--listTitle [listTitle]`
+: Title of the list if you want to update a list content type. Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listId [listId]`
+: ID of the list if you want to update a list content type. Specify either `listTitle`, `listId` or `listUrl`.
+
+`--listUrl [listUrl]`
+: URL of the list if you want to update a list content type. Specify either `listTitle`, `listId` or `listUrl`.
+
+--8<-- "docs/cmd/_global.md"
+
+## Examples
+
+Move site content type to a different group
+
+```sh
+m365 spo contenttype set --id 0x001001 --webUrl https://contoso.sharepoint.com --Group "My group"
+```
+
+Rename list content type
+
+```sh
+m365 spo contenttype set --name "My old item" --webUrl https://contoso.sharepoint.com --listTitle "My list" --Name "My item"
+```

package/docs/docs/cmd/spo/list/list-roleassignment-add.md

@@ -26,10 +26,10 @@ m365 spo list roleassignment add [options]
 : SharePoint ID of principal it may be either user id or group id we want to add permissions to. Specify principalId only when upn or groupName are not used.
 
 `--upn [upn]`
-: Upn/email of user to assign role to. Specify either upn or princpialId
+: Upn/email of user to assign role to. Specify either upn or principalId
 
 `--groupName [groupName]`
-: Enter group name of Azure AD or SharePoint group.. Specify either groupName or princpialId
+: Enter group name of Azure AD or SharePoint group.. Specify either groupName or principalId
 
 `--roleDefinitionId [roleDefinitionId]`
 : ID of role definition. Specify either roleDefinitionId or roleDefinitionName but not both

package/docs/docs/cmd/spo/list/list-roleassignment-remove.md

@@ -26,10 +26,10 @@ m365 spo list roleassignment remove [options]
 : SharePoint ID of principal it may be either user id or group id we want to remove permissions Specify principalId only when upn or groupName are not used.
 
 `--upn [upn]`
-: upn/email of user. Specify either upn or princpialId.
+: upn/email of user. Specify either upn or principalId.
 
 `--groupName [groupName]`
-: enter group name of Azure AD or SharePoint group. Specify either groupName or princpialId.
+: enter group name of Azure AD or SharePoint group. Specify either groupName or principalId.
 
 `--confirm`
 : Don't prompt for confirming removing the role assignment

package/docs/docs/cmd/spo/listitem/listitem-roleassignment-remove.md

@@ -1,6 +1,6 @@
 # spo listitem roleassignment remove
 
-Removes a role assignment to a listitem.
+Removes a role assignment from a listitem.
 
 ## Usage
 
@@ -29,10 +29,10 @@ m365 spo listitem roleassignment remove [options]
 : SharePoint ID of principal it may be either user id or group id we want to remove permissions Specify principalId only when upn or groupName are not used.
 
 `--upn [upn]`
-: upn/email of user. Specify either upn or princpialId.
+: upn/email of user. Specify either upn or principalId.
 
 `--groupName [groupName]`
-: enter group name of Azure AD or SharePoint group. Specify either groupName or princpialId.
+: enter group name of Azure AD or SharePoint group. Specify either groupName or principalId.
 
 `--confirm`
 : Don't prompt for confirming removing the role assignment

package/docs/docs/cmd/spo/roledefinition/roledefinition-add.md

@@ -0,0 +1,43 @@
+# spo roledefinition add
+
+Adds a new roledefinition to web
+
+## Usage
+
+```sh
+m365 spo roledefinition add [options]
+```
+
+## Options
+
+`-u, --webUrl <webUrl>`
+: URL of the site to which role should be added
+
+`-n, --name <name>`
+: role definition name
+
+`-d, --description [description]`
+: role definition description
+
+`--rights [rights]`
+: A case-sensitive string array that contain the permissions needed for the custom action. Allowed values `EmptyMask,ViewListItems,AddListItems,EditListItems,DeleteListItems,ApproveItems,OpenItems,ViewVersions,DeleteVersions,CancelCheckout,ManagePersonalViews,ManageLists,ViewFormPages,AnonymousSearchAccessList,Open,ViewPages,AddAndCustomizePages,ApplyThemeAndBorder,ApplyStyleSheets,ViewUsageData,CreateSSCSite,ManageSubwebs,CreateGroups,ManagePermissions,BrowseDirectories,BrowseUserInfo,AddDelPrivateWebParts,UpdatePersonalWebParts,ManageWeb,AnonymousSearchAccessWebLists,UseClientIntegration,UseRemoteAPIs,ManageAlerts,CreateAlerts,EditMyUserInfo,EnumeratePermissions,FullMask`. Default `EmptyMask`
+
+--8<-- "docs/cmd/_global.md"
+
+## Remarks
+
+The `--rights` option accepts **case-sensitive** values.
+
+## Examples
+
+Adds the role definition for site _https://contoso.sharepoint.com/sites/project-x_ with name _test_
+
+```sh
+m365 spo roledefinition add --webUrl https://contoso.sharepoint.com/sites/project-x --name test
+```
+
+Adds the role definition for site _https://contoso.sharepoint.com/sites/project-x_ with name _test_ and description _test description_ and rights _ViewListItems,AddListItems,EditListItems,DeleteListItems_
+
+```sh
+m365 spo roledefinition add --webUrl https://contoso.sharepoint.com/sites/project-x --name test --description "test description" --rights "ViewListItems,AddListItems,EditListItems,DeleteListItems"
+```

package/docs/docs/cmd/spo/site/site-apppermission-add.md

@@ -14,7 +14,7 @@ m365 spo site apppermission add [options]
 : URL of the site collection to add the permission
 
 `-p, --permission <permission>`
-: Permission to site (`read`, `write`, or `owner`)
+: Permission to site (`read`, `write`, `manage` or `fullcontrol`)
 
 `-i, --appId [appId]`
 : Client ID of the Azure AD app for which to grant permissions

package/docs/docs/cmd/spo/site/site-apppermission-set.md

@@ -23,7 +23,7 @@ m365 spo site apppermission set [options]
 : Display name of the Azure AD app for which to update permissions. Specify `permissionId`, `appId` or `appDisplayName`
 
 `-p, --permission <permission>`
-: Permission to site (`read`, `write`, or `owner`)
+: Permission to site (`read`, `write`, `manage` or `fullcontrol`)
 
 --8<-- "docs/cmd/_global.md"
 

package/docs/docs/cmd/spo/web/web-roleassignment-add.md

@@ -17,10 +17,10 @@ m365 spo web roleassignment add [options]
 : SharePoint ID of principal it may be either user id or group id we want to add permissions to. Specify principalId only when upn or groupName are not used.
 
 `--upn [upn]`
-: upn/email of user to assign role to. Specify either upn or princpialId
+: upn/email of user to assign role to. Specify either upn or principalId
 
 `--groupName [groupName]`
-: enter group name of Azure AD or SharePoint group.. Specify either groupName or princpialId
+: enter group name of Azure AD or SharePoint group.. Specify either groupName or principalId
 
 `--roleDefinitionId [roleDefinitionId]`
 : ID of role definition. Specify either roleDefinitionId or roleDefinitionName but not both

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnp/cli-microsoft365",
-  "version": "5.8.0-beta.bc15f2b",
+  "version": "5.8.0-beta.c1d5041",
   "description": "Manage Microsoft 365 and SharePoint Framework projects on any platform",
   "license": "MIT",
   "main": "./dist/api.js",
@@ -138,6 +138,7 @@
     "Kelkar, Vipul <vipul.kelkar@outlook.com>",
     "Kesavanarayanan, Sudharsan <10280385+sudharsank@users.noreply.github.com>",
     "Khalil, Bassem <bk@bassems-air.home>",
+    "Kirkham, Don <donkirkham@live.com>",
     "Kumar, Shantha <34408892+ktskumar@users.noreply.github.com>",
     "Lamber, Patrick <patrick@nubo.eu>",
     "Laskewitz, Daniel <daniel@laskewitz.nl>",