feat: avm/res/desktop-virtualization/host-pool

[moisesjgomez]

Description

Closes avm/res/desktop-virtualization/host-pool #144

Adding a new module

• A proposal has been submitted and approved.
• I have included "Closes #{module_proposal_issue_number}" in the PR description.
• I have run brm validate locally to verify the module files.
• I have run deployment tests locally to ensure the module is deployable.

[moisesjgomez]

Updates have been made and badge up to date. @ChrisSidebotham One failure on PSRule due to secure parameter rule picking up term "key" on parameters even though they are not secrets.

[ChrisSidebotham]

Updates have been made and badge up to date. @ChrisSidebotham Chris Sidebotham FTE One failure on PSRule due to secure parameter rule picking up term "key" on parameters even though they are not secrets.

@BernieWhite - Looking into this issue we need a way to supress a rule for a single parameter, is this possible with the current release? As described above we have an issue in this workflow with 3 individual parameters in which are not actually secret values but being flagged as Should be marked as @secure due to the name containing secret and key and possibly token

[BernieWhite]

@ChrisSidebotham Yes you are able to configure AZURE_DEPLOYMENT_NONSENSITIVE_PARAMETER_NAMES as of v1.31.1 to ignore parameters by name.

https://azure.github.io/PSRule.Rules.Azure/setup/configuring-rules/#azure_deployment_nonsensitive_parameter_names

[ChrisSidebotham]

@moisesjgomez - I see you indented secrets, this is not hte issue we need a new line (empty) at the bottom of the YAML file