-
-
Notifications
You must be signed in to change notification settings - Fork 874
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
Implement support for National cloud deployments (Issue #937) #938
Conversation
abraunegg
commented
May 28, 2020
- Implement support for National cloud deployments as per https://docs.microsoft.com/en-us/graph/deployments
* Implement support for National cloud deployments as per https://docs.microsoft.com/en-us/graph/deployments
* Add documentation for option
* Update readme
Update documentation
Update readme
* Remove debug logging
* Clarify what entries are for what national region
* Update configuration document
* Add images
* Add further images
* Update wording
* text updates
* update wording
* Use right image
* Add API permissions as table before image
* Remove .
@norbusan Documentation for this feature 'looks' right based on existing application configuration, but again, no way to test (except for using new application id which we know works) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like you, I cannot actually test it, but the changes look reasonable
* Generage a /delta compatible response when using National Azure AD deployments that do not support /delta queries
* USL4 needs to be checked
* Add error handling for OneDrive Exceptions (HTTP errors etc)
* Add logging so the user 'knows' that stuff is being queried ... otherwise the OneDrive walk is occuring .. and there is zero visibility what is going on
* Update error handling that makes more sense
* Handle nextLink when /children responses have greater than 200 elements
* Add folder being scanned to better show progress
* Handle remote deletes when /delta is not possible by flagging all files as in-sync, but if using National Cloud Deployment, before calling /children, flag all files as out-of-sync locally. As each JSON response from OneDrive is processed, it resets the flag for that item as being 'in-sync', thus we can query those that were not set, thus, those are files that were remove from OneDrive, and should be removed locally.
* resetting this to false (was true) to test locally
@norbusan When in use, the output is like this:
Deleting data on OneDrive:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Alex,
since I cannot test, I only read through the massive changes ... not that I can say from reading that this is semantically correct.
The is one comment about the storage size/type of the syncStatus, but that is not that important.
You should be able to test this - if you 'modify' manually sync.d:
to
This will 'bypass' the checks where the flag gets set, and uses all the new code, but without using the National Azure Deployment ... it is how I have been testing. |
* Add NCD check to new --monitor DB scan function
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |