Closed juliamwang6 closed 1 year ago
The known workaround for this limitation is that each class-based resource needs to have their own prefix for common types/enums like FileEnsure
instead of just Ensure
. See our docs: https://learn.microsoft.com/en-us/powershell/dsc/tutorials/create-dsc-resource-machine-config?view=dsc-2.0#add-the-ensure-property
Closing now that the workaround is publily documented
[like] Julia Wang reacted to your message:
From: Michael Greene @.> Sent: Tuesday, May 30, 2023 7:20:01 PM To: Azure/nxtools @.> Cc: Julia Wang @.>; Author @.> Subject: Re: [Azure/nxtools] Known issue with multiple class-based resources (Issue #15)
Closing now that the workaround is publily documented
— Reply to this email directly, view it on GitHubhttps://github.com/Azure/nxtools/issues/15#issuecomment-1568953268, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3O3A5AKGUHYP74N4VJ6PPLXIZB6DANCNFSM6AAAAAAWGZSIEE. You are receiving this because you authored the thread.Message ID: @.***>
Known issue: you currently cannot use two different kinds of class-based resources in the same mof file. We are actively working with the PowerShell team to fix this.