Create separate folder per module containing scripts to be executed on import

[maddieclayton]

Description

#4855

---

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

• I have read the contribution guidelines.
• If changes were made to any cmdlet, the XML help was regenerated using the platyPSHelp module.
• If any large changes are made to a service, they are reflected in the respective change log.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
• The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

• Pull request includes test coverage for the included changes.
• PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

• New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
• Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

• Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
• Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
• Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

[cormacpayne]

@maddieclayton a few modules currently have <SERVICE>Startup.ps1 scripts that get ran when their module is imported:

• AnalysisServices
• Cdn
• HDInsight
• Network
• OperationalInsights
• Profile
• RecoveryServices.SiteRecovery
• RecoveryServices
• Sql
• Websites

These modules have a class that implements IModuleAssemblyInitializer, which overrides the OnImport() method and runs the startup script. I think we should move the startup script to the corresponding StartupScripts folder and remove the IModuleAssemblyInitializer inheritance where we can (it looks like this should be everywhere but Profile). Then we would just need to verify the scripts ran after a successful packaging job.

[markcowl]

Remove the extra ItemGroup

[markcowl]

Mor module that don't yet have this, I would comment this out so we don't have an unnecessary dot-include in the psm1.

[cormacpayne]

@azuresdkci test this please

[cormacpayne]

@maddieclayton you'll need to regenerate the .wxi file since you are removing the startup scripts that were packaged into the installer

[markcowl]

on demand run here:https://azuresdkci.westus2.cloudapp.azure.com/view/PowerShell/job/powershell-demand/234/
signign run here:https://azuresdkci.westus2.cloudapp.azure.com/view/PowerShell/job/powershell-sign/29/

@maddieclayton Need to verify a sample of aliases from each module before merging

[maddieclayton]

on demand here: https://azuresdkci.westus2.cloudapp.azure.com/view/PowerShell/job/powershell-demand/257/
sign job here: https://azuresdkci.westus2.cloudapp.azure.com/view/PowerShell/job/powershell-sign/40/

[maddieclayton]

@markcowl can you take a quick look? I've changed a fair amount since you've approved. On demand passed and sign job is working (I check the aliases for each module with a startup script).