-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug report: spo tenant recyclebinitem restore
doesn't restore group
#6021
Comments
milanholemans
added
bug
needs peer review
Needs second pair of eyes to review the spec or PR
labels
May 4, 2024
Good catch. Let's create a separate issue for fixing showing the error message |
waldekmastykarz
added
help wanted
and removed
needs peer review
Needs second pair of eyes to review the spec or PR
labels
May 8, 2024
Is that necessary? The only thing we have to do to fix this is add a response type in the request object. cli-microsoft365/src/m365/spo/commands/tenant/tenant-recyclebinitem-restore.ts Lines 70 to 79 in d3d4146
|
Can I work on this? |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Priority
(Medium) I'm annoyed but I'll live
Description
When using
spo tenant recyclebinitem restore
on a team site, the connected group remains in the recycle bin.Steps to reproduce
Run
m365 spo tenant recyclebinitem restore -u https://contoso.sharepoint.com/sites/Marketing
on any teams site in the SharePoint recycle bin with its connected group in the group recycle bin.Expected results
Restore both the group and the site.
Actual results
Only the site is restored, not the group.
Diagnostics
No response
CLI for Microsoft 365 version
v7.8.0
nodejs version
v20.10.0
Operating system (environment)
Windows
Shell
PowerShell
cli doctor
No response
Additional Info
In this command, we're using a
SPOInternalUseOnly.Tenant
endpoint. However it seems like the UI is using the same request, the UI restores the group without any problem, while this command doesn't.Maybe we should look to an alternative endpoint.
The text was updated successfully, but these errors were encountered: