Skip to content
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

GC: Implement restore of DataCollection object #181

Closed
dadams39 opened this issue Jun 10, 2022 · 3 comments
Closed

GC: Implement restore of DataCollection object #181

dadams39 opened this issue Jun 10, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@dadams39
Copy link
Contributor

This is a preliminary function to inform CLI design.

A data collection object has n M365 objects for a user. The function calling signature for GC ->

(gc *GraphConnector) restoreCollection( dc DataCollection)

Unknowns
What is the desired output for success or failure?

Known
Microsoft Graph does not support the uploading large objects.
microsoftgraph/msgraph-sdk-go-core#1
This is issue number 12.

@dadams39 dadams39 added the enhancement New feature or request label Jun 10, 2022
@dadams39 dadams39 self-assigned this Jun 10, 2022
@dadams39
Copy link
Contributor Author

return -> error
Current API requires that user.GetId() for UsersById. Previous version allowed for user@domain.
The message will fall to be restored if the message is in the directory.
Additionally, the MailFoldersById can be set with the display name (e.g. Inbox)

Should restore files go in a special directory for the user?

@dadams39
Copy link
Contributor Author

PR #197 awaiting review

dadams39 pushed a commit that referenced this issue Jun 14, 2022
Addition of restoreMessages(dc DataCollection) error for GraphConnector
Merge completes Issue #181. Test suites updated
@dadams39
Copy link
Contributor Author

PR complete. Issue closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant