feat: Pattern modules for policy exemptions

[oZakari]

Description

Adds the pattern modules for Policy Exemptions

Closes Azure/Azure-Verified-Modules#1735

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

[oZakari]

Hi team, I assume the telemetry errors and the module identifier errors are related to the directory structure for this pattern module (similar to the ALZ Policy Assignments Pattern module) and this file? Anything I need to do on my side?

[oZakari]

Hi team, I assume the telemetry errors and the module identifier errors are related to the directory structure for this pattern module (similar to the ALZ Policy Assignments Pattern module) and this file? Anything I need to do on my side?

Hi @Azure/avm-core-team, any update on this one?

[AlexanderSehr]

Hey @oZakari,
sorry has been a busy week. Will try to squeeze the review in

[AlexanderSehr]

Either the team is not created or not yet approved in the hierachy (ref)

[oZakari]

Got it, must be that it hasn't been approved yet then as it exists here.

[AlexanderSehr]

Hey @oZakari, please don't resolve a comment unless it's a code suggestion 😉 Makes re-reviews a bit harder.
In this case this must remain a blocking comment until the group was approved. It could lead to issues if we merge the module before.

[oZakari]

Bumping as tests are still failing for group approval. @matebarabas

[oZakari]

Hey @oZakari, sorry has been a busy week. Will try to squeeze the review in

No worries at all, @AlexanderSehr! Thank you for taking the time to review it—I just wanted to make sure it was on your radar. Really appreciate it! 😊

[jtracey93]

Hey @oZakari ,

Firstly, thanks for your work on this PR!

We have made some changes to the AVM CI, detailed below, which means we need you to update your fork to pull in these latest changes and re-run your tests to show they still are passing prior to approving and merging this PR, as we don't and it fails once merged the publishing of your module will fail and will be blocked going forward until the test pass again via additional PRs.

Changes to CI That Have Been Made That You Need To Take Action On

• feat: Add WAF Security PS Rule Config #3745
  • Adds WAF Security PSRule Checks using this custom baseline of rules (/avm/utilities/pipelines/staticValidation/psrule/.ps-rule/cb-waf-security.Rule.yaml)
  • Action Required By You:
    • Ingest/pull-in these changes into your PR branch and re-run your tests to ensure they pass
      • If any issues with the rules and you think it should apply, please ping/reach out to the core team

Any questions reach out to the AVM Core Team by tagging us in your PR here or internally via Teams

Thanks

Jack (AVM Core Team)

[oZakari]

Hey @oZakari ,

Firstly, thanks for your work on this PR!

We have made some changes to the AVM CI, detailed below, which means we need you to update your fork to pull in these latest changes and re-run your tests to show they still are passing prior to approving and merging this PR, as we don't and it fails once merged the publishing of your module will fail and will be blocked going forward until the test pass again via additional PRs.

Changes to CI That Have Been Made That You Need To Take Action On

• feat: Add WAF Security PS Rule Config #3745

  • Adds WAF Security PSRule Checks using this custom baseline of rules (/avm/utilities/pipelines/staticValidation/psrule/.ps-rule/cb-waf-security.Rule.yaml)

  • Action Required By You:

    • Ingest/pull-in these changes into your PR branch and re-run your tests to ensure they pass

      • If any issues with the rules and you think it should apply, please ping/reach out to the core team

Any questions reach out to the AVM Core Team by tagging us in your PR here or internally via Teams

Thanks

Jack (AVM Core Team)

Hey @oZakari ,

Firstly, thanks for your work on this PR!

We have made some changes to the AVM CI, detailed below, which means we need you to update your fork to pull in these latest changes and re-run your tests to show they still are passing prior to approving and merging this PR, as we don't and it fails once merged the publishing of your module will fail and will be blocked going forward until the test pass again via additional PRs.

Changes to CI That Have Been Made That You Need To Take Action On

• feat: Add WAF Security PS Rule Config #3745

  • Adds WAF Security PSRule Checks using this custom baseline of rules (/avm/utilities/pipelines/staticValidation/psrule/.ps-rule/cb-waf-security.Rule.yaml)

  • Action Required By You:

    • Ingest/pull-in these changes into your PR branch and re-run your tests to ensure they pass

      • If any issues with the rules and you think it should apply, please ping/reach out to the core team

Any questions reach out to the AVM Core Team by tagging us in your PR here or internally via Teams

Thanks

Jack (AVM Core Team)

Thanks, my branch has been updated.

[oZakari]

Hey @AlexanderSehr, should be good for you to review now. Thanks!