MicrosoftLearning / MicrosoftLearning/mslearn-mlops

Lab 05, Replace GUID-based suffix generation with Lab Instance ID throughout MLOps lab

Open
#74 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
40
Forks
90
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search setup-prod-design.sh, setup-mlops-envs.sh, setup.sh, setup1.sh, and the lab instructions for GUID-based suffix generation and resource-name examples. Replace those references with the Lab Instance ID convention, then check screenshots and expected output for remaining GUID-based names. Done means all listed resources consistently use the expected rg-ai300, mlw-ai300, and mlr-ai300 naming patterns.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, bash
Domain
cloud, devops, documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.