importer-msgraph-metadata: Add workarounds for several bugs in Graph Api Spec #4519
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes some bugs I encountered whilst using the Graph SDK generated by pandora.
Model
microsoft.graph.connectedOrganization
The field
identitySources
cannot be read-only, as it needs to be set when creating a new connected organization.Docs Ref: https://learn.microsoft.com/en-us/graph/api/entitlementmanagement-post-connectedorganizations?view=graph-rest-beta&tabs=http#request
Model
microsoft.graph.crossTenantAccessPolicyConfigurationPartner
The field
tenantId
cannot be read-only, otherwise it is impossible to create a new cross tenant access policy partner organization.Docs Ref: https://learn.microsoft.com/en-us/graph/api/crosstenantaccesspolicy-post-partners?view=graph-rest-1.0&tabs=http#request
Model
microsoft.graph.unifiedRoleManagementPolicy
The fields
lastModifiedBy
andlastModifiedDateTime
must be read only, as they can only be modified by the backend service. Attempting to set them results in HTTP Error 400 Bad Request.Docs Ref: https://learn.microsoft.com/en-us/graph/api/unifiedrolemanagementpolicy-update?view=graph-rest-1.0&tabs=http#request