I have a resource that requires the ActiveDirectory module. Previously I would just use a DSC WindowsFeature resource to ensure it was installed prior to the DSC resource that requires it runs.
Since upgrading to PSv5 Production Preview, when it tries to apply the configuration it errors with:
Importing module POSH_xADOrganizationalUnit failed with error - The script 'POSH_xADOrganizationalUnit.psm1' cannot be run because the following modules that are specified by the "#requires" statements of the script are missing: ActiveDirectory.
The dependencies are still there, so I’m assuming it is preloading all the modules before applying. Should this method still work with the dependencies or do I need to adjust my DSC resource to check for the module and install it itself if it doesn’t exist? That would be fine if I should do that, but I have other DSC resources that require modules that are installed via installers (MSI) and use the same dependency to make sure it is installed before the resource that needs it runs.
Update: I did verify the generated MOF has the correct dependencies listed.