azure-sdk-for-net: [BUG] `Microsoft.Azure.Graph.RBAC.Models.DirectoryObject` is missing all expandable properties
Describe the bug
If you browse the OData API (https://graph.windows.net/tenantid/$metadata), you will see the DirectoryObject has the following properties:
objectTypeobjectIddeletionTimestamp
and the following navigation properties:
createdOnBehalfOfcreatedObjectsmanagerdirectReportsmemberstransitiveMembersmemberOftransitiveMemberOfownersownedObjects
The problem is that all the navigation properties are not present in the DirectoryObject model.
Expected behavior
The navigation properties should be there.
Actual behavior (include Exception or Stack Trace)
There is no way to get the navigation properties, so no stack trace.
To Reproduce
no reproduction possible.
Environment:
not relevant. Is broken everywhere
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 23 (12 by maintainers)
@paule96: If you don’t mind opening an issue in the PowerShell repository, that is likely to be the most expedient path forward. With no known owner for for the Graph RBAC library, it would probably be one of the folks involved in this thread who would reach out to the PowerShell team via a GitHub issue to make them aware. You are likely to carry more weight, as you have a real-world driver for the change.
Please feel free to mention myself, @ramya-rao-a, and @AlexGhiondea in as needed if we can help with the resulting discussion there.
Thank you for your feedback. Tagging and routing to the team best able to assist.
Hi, we’re sending this friendly reminder because we haven’t heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don’t hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
Hi @paule96. Apologies for not touching base sooner. Unfortunately, though we’ve continued to dig in we’ve still not been able to locate the owner of the library. At this point, I’ve been going through the commit history and reaching out to those that contributed and who still work for Microsoft in the hope of finding some insight. This morning, I reached out a small set of contributors from 5 years ago… so we’re pretty close to the end of that.
There’s also been discussion happening at the leadership levels to try and understand that the future plans and directions are for the library, but I don’t have any updates there nor any deep insight into the process.
This is the part where I apologize, again, that you’ve been waiting for so long… though I imagine that it is starting to feel rather disingenuous.
Just a quick note, there is still discussion ongoing internally. One key contact was out through last week. We apologize for the delay and confusion surrounding ownership here.
No updates; the email thread was kicked but, as mentioned, the US holiday last week had many folks out. I’ll kick it next on Wednesday, to give some time for those returning to get through their email backlog.
Unfortunately, I’m only serving as first-line triage in this case. I don’t have insight into the process that is used by the team that owns this library. Generally, there’s a 72 hour window provided for teams to triage and respond. If we don’t see engagement by the owners after 72 hours, please feel free to ping me again and I’ll do what I’m able to escalate.