feat: avm/ptn/data/private-analytical-workspace V0.1

[jbinko]

Description

This is the initial implementation of the proposed pattern module detailed in proposal. Azure/Azure-Verified-Modules#949 It includes documentation, unit tests, and PowerShell post-unit tests.

Pipeline Reference

Pipeline

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings

[AlexanderSehr]

Small addition: It seems to be related to: PowerShell/PowerShell#23197 (comment)
Currently testing if we still need the explicit pwsh version installation (which was added due to a bug of a version). If we do, then we need to hardcode the runner version

[jbinko]

OK, all changes completed on my side. Ready for merge. Tests and deployments are passing. @AlexanderSehr pipeline succeeds if I do changes you proposed in the file \avm\utilities\pipelines\sharedScripts\Set-EnvironmentOnAgent.ps1. Those changes are not included in this PR. I removed them after try. I expect this will be changed in the main in original repo.

[AlexanderSehr]

Hey @jbinko,
there are 2 final comments hidden behind this GitHub feature 😄

[jbinko]

Hey @jbinko, there are 2 final comments hidden behind this GitHub feature 😄

Thanks @AlexanderSehr - got it. I fixed the remove of default test location and virtual network name propagation into dependencies files in tests.

Should be ready for merge now.

[AlexanderSehr]

Hey @jbinko,
please not that many of the module's post-deployment tests did fail in the upstream workflow (ref). That means the module was not published. Could you please check if you can reproduce the errors you can see in the workflow's log? The deployment seemed to have worked.

[jbinko]

Hey @jbinko, please not that many of the module's post-deployment tests did fail in the upstream workflow (ref). That means the module was not published. Could you please check if you can reproduce the errors you can see in the workflow's log? The deployment seemed to have worked.

Thanks @AlexanderSehr, I created new PR #3626 which addresses the post deployment tests issue.
The tests are run by default in the fixed location North Europe