jambar42

The existing `set` code results in a second, explicit object permission entry even when the inherited entry already exists. I guess this isn't a blocker, it just makes the permissions...

Here's a `HyperVDSC` module that contains the `VMNetworkAdapterTeamMapping` https://github.com/rchaganti/HyperVDsc/blob/dev/DSCResources/VMNetworkAdapterTeamMapping/VMNetworkAdapterTeamMapping.psm1 https://github.com/rchaganti/HyperVDsc I've found that in our environments we've needed to use both the above rchaganti/HyperVDsc as well as xHyperV to meet...

It seems the way SqlSetup and SqlServiceAccount handle the GMSA is different. SqlSetup wraps the calls to `Get-ServiceAccount` into a [Get-ServiceAccountParameters](https://github.com/dsccommunity/SqlServerDsc/blob/e0bf6a5e127bf4bce95a5c4ac3b6b67b66da08e4/source/DSCResources/DSC_SqlSetup/DSC_SqlSetup.psm1#L2467) which excludes the password.

We have a few scenarios where we want the reboot behavior to be variable based on the current context. Currently when a resource needs a reboot, we set `$Global:DSCMachineStatus =...

I like the idea of having a Settings file with each resource / configuration used as an override to the higher level Settings. This is similar to how it is...