Since we don’t use the
RootModule key in the module manifest, we should not
NestedModules key to add modules that export commands that are shared
between resource modules.
Normally, a single list in the
RootModule key, can restrict what is
exported using the cmdlet
Export-ModuleMember. Since we don’t use the
key we can’t restrict what is exported, so every nested module will export all the
commands (or all the commands restricted by
Export-ModuleMember in that
individual nested module). If two resource modules were to use the
method, it would result in one of them being unable to install since they have
conflicting exported commands.