Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: automation account deployment test failure due to linked Log Ana…
…lytics region (#4348) ## Description Automation account testing pipeline is failing since days, for "Error - chosen Azure Automation does not have a Log Analytics workspace linked for operation to succeed." This affects deployments in default eastUs https://learn.microsoft.com/en-us/azure/automation/how-to/region-mappings This PR solves the issue by enforcing test location. closes #4090 ## Pipeline Reference | Pipeline | | -------- | | [](https://github.com/elanzel/bicep-registry-modules/actions/workflows/avm.res.automation.automation-account.yml) | ## Type of Change - [ ] Update to CI Environment or utilities (Non-module affecting changes) - [ ] Azure Verified Module updates: - [x] 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. - [x] 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 - [x] I'm sure there are no other open Pull Requests for the same update/change - [x] I have run `Set-AVMModule` locally to generate the supporting module files. - [x] My corresponding pipelines / checks run clean and green without any errors or warnings
- Loading branch information