Currently a junction named AzureRM is created under ..\Scoop\modules directory that points to ..\Scoop\apps\azure-ps\current directory.
However, the package is not a single PowerShell module, but a collection of modules, and while cmdlets are still found, and modules loaded on first reference (assuming ..\Scoop\modules is present in psmodulepath environment variable), importing modules with import-module doesn't work (I think it has to do with modules being well-formed).
My proposal is to change the behavior so that each module sub-directory in ..\Scoop\apps\azure-ps\current is added as a distinct junction directory directly under ..\Scoop\modules.
My current workaround is to execute the following code after installation:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Currently a junction named
AzureRM
is created under..\Scoop\modules
directory that points to..\Scoop\apps\azure-ps\current
directory.However, the package is not a single PowerShell module, but a collection of modules, and while cmdlets are still found, and modules loaded on first reference (assuming
..\Scoop\modules
is present inpsmodulepath
environment variable), importing modules withimport-module
doesn't work (I think it has to do with modules being well-formed).My proposal is to change the behavior so that each module sub-directory in
..\Scoop\apps\azure-ps\current
is added as a distinct junction directory directly under..\Scoop\modules
.My current workaround is to execute the following code after installation: