The lab currently uses GUID-generated suffixes in both the provisioning scripts and lab instructions.
This causes resource names to diverge from the Azure Policy naming requirements and prevents resources from matching ACP constraints.
Update all scripts and instructions that reference GUID-based naming to use the Skillable Lab Instance ID instead.
Current:
guid=$(cat /proc/sys/kernel/random/uuid)
suffix=${guid//[-]/}
suffix=${suffix:0:18}
Proposed:
suffix=$(whoami | cut -d'-' -f2)
Updates required:
- setup-prod-design.sh
- setup-mlops-envs.sh
- setup.sh
-setup1.sh
- Any instruction steps that reference GUID generation
- Any screenshots, examples, or expected output that contain GUID-based resource names
Expected naming convention:
rg-ai300-l
mlw-ai300-l
rg-ai300-dev-
mlw-ai300-dev-
rg-ai300-prod-
mlw-ai300-prod-
rg-ai300-reg-
mlr-ai300-shared-
This change aligns all generated resources with the ACP naming requirements and ensures deterministic resource names across lab runs.
The lab currently uses GUID-generated suffixes in both the provisioning scripts and lab instructions.
This causes resource names to diverge from the Azure Policy naming requirements and prevents resources from matching ACP constraints.
Update all scripts and instructions that reference GUID-based naming to use the Skillable Lab Instance ID instead.
Current:
guid=$(cat /proc/sys/kernel/random/uuid)
suffix=${guid//[-]/}
suffix=${suffix:0:18}
Proposed:
suffix=$(whoami | cut -d'-' -f2)
Updates required:
-setup1.sh
Expected naming convention:
rg-ai300-l
mlw-ai300-l
rg-ai300-dev-
mlw-ai300-dev-
rg-ai300-prod-
mlw-ai300-prod-
rg-ai300-reg-
mlr-ai300-shared-
This change aligns all generated resources with the ACP naming requirements and ensures deterministic resource names across lab runs.