-
Notifications
You must be signed in to change notification settings - Fork 515
o365: tolerate changed API next page URI behaviour #15325
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
Conversation
The API now returns the next page URI with the parameters lowercased. This is not documented[1], so retain support for the document behaviour. [1]https://learn.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-reference
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @efd6 |
|
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
andrewkroh
left a comment
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.
LGTM.
|
Package o365 - 2.29.0 containing this change is available at https://epr.elastic.co/package/o365/2.29.0/ |
chrisberkhout
left a comment
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.
👍
The API now returns the next page URI with the parameters lower-cased. This is not documented[1], so also retain support for the documented behaviour. [1]https://learn.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-reference




Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots