Azure / Azure/bicep-registry-modules

[AVM Module Issue]: Automation Account - Hybrid Worker Group deployment name

Open
#7,253 1 comment 0 reactions 1 assignee Claimed by @gpacetti View on GitHub
Class: Resource Module :package: Needs: Triage :mag: Type: AVM :a: :v: :m:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 10h
Merged PRs (30d)
27

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Bug

### Module Name

avm/res/automation/automation-account

### (Optional) Module Version

0.19

### Description

The name of the Hybrid Worker Group deployment uses the same name in the loop of the Hybrid Worker Group Worker, causing a name collision from the inner deployment with it's current in-flight parent deployment

[main.bicep](https://github.com/Azure/bicep-registry-modules/blob/main/avm/res/automation/automation-account/main.bicep#L454): '${uniqueString(subscription().id, resourceGroup().id)}-AutoAccount-HybridWorkerGroup-Worker-${index}'

[hybrid-runbook-worker-group/main.bicep](https://github.com/Azure/bicep-registry-modules/blob/main/avm/res/automation/automation-account/hybrid-runbook-worker-group/main.bicep#L58): '${uniqueString(subscription().id, resourceGroup().id)}-AutoAccount-HybridWorkerGroup-Worker-${index}'

Proposal:

Change [main.bicep](https://github.com/Azure/bicep-registry-modules/blob/main/avm/res/automation/automation-account/main.bicep#L454) to use AutoAccount-HybridWorkerGroup to build the parent deployment name

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.