New-M365DSCResource - help for Graph-resources without any New-xx cmdlet. about microsoft365dsc HOT 4 OPEN

This looks like an update for the DRG to allow either Set or New cmdLets to be used for the generation of new resources. Is there any New- equivalent for MgPolicyCrossTenantAccessPolicyPartnerIdentitySynchronization ?

from microsoft365dsc.

Not that I know of. It looks like a kind of throwback to the old MSOL-days. We have Get-, Set- and Remove-cmdlets.

from microsoft365dsc.

Part of the issue at hand seems to be that one - perhaps both - of the templates that DRG uses to build the module for a new DSC-resource assumes that must exist for any Graph-resource.
For MgPolicyCrossTenantAccessPolicyPartnerIdentitySynchronization, Set- is the equivalent to New-
This could be handled in the same way that DRG chooses an updateVerb that is either Update or Set based on cmdlet-availability. I think the same could be achieved if a check is included to see if a New- cmdlet actually exists or else use the chosen updateVerb as the newVerb.
If time permits, I'll have a go at this myself.

from microsoft365dsc.

A related issue with the DRG is that resources that only provide Get- and Set- but not New- cmdlets may not contain 'variants' of type List and will thus fail to find a 'repository' nor an 'assignment' cmdlet and will then throw an exception.
A related issue is that when there's no New- cmdlet then there's no Create parameterset, causing an additional exception later on.
I've tried various 'fixes' but something unexpected keeps popping up.

from microsoft365dsc.