You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the ADO logs, it looks like Compliance module fails to build when targeting the latest API changes due to:
A circular reference in microsoft.graph.ediscovery.sourceCollection:
Cmdlet name conflict in *-MgComplianceEdiscoveryCaseNoncustodialDataSource. AutoREST resolves /compliance/ediscovery/cases/{case-id}/noncustodialDataSources/{noncustodialDataSource-id} and /compliance/ediscovery/cases/{case-id}/noncustodialDataSources/{noncustodialDataSource-id}/dataSource to the same cmdlet name.
Integrated build pipeline is not reporting build errors when executing in parallel.
The first two can easily be resolved via AutoREST directives. AB#7992
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
From the ADO logs, it looks like
Compliance
module fails to build when targeting the latest API changes due to:microsoft.graph.ediscovery.sourceCollection
:*-MgComplianceEdiscoveryCaseNoncustodialDataSource
. AutoREST resolves/compliance/ediscovery/cases/{case-id}/noncustodialDataSources/{noncustodialDataSource-id}
and/compliance/ediscovery/cases/{case-id}/noncustodialDataSources/{noncustodialDataSource-id}/dataSource
to the same cmdlet name.The first two can easily be resolved via AutoREST directives.
AB#7992
The text was updated successfully, but these errors were encountered: