MicrosoftLearning / MicrosoftLearning/mslearn-mlops

Lab 05 Add Dev workspace creation step before environment-specific data asset creation

Open Beginner friendly
#75 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 asks learners to create a production workspace and then immediately proceeds to creating development and production data assets.

However, the development workspace and resource group are never explicitly created before those commands are used.

Add a new step between:

Step 5: "Plan the commands that would create the production resource group and workspace..."

and

Step 6: "Finally, plan the data assets that keep development and production data separate..."

The new step should create the development resource group and Azure Machine Learning workspace:

Create the dev resource group

az group create --name $DEV_RESOURCE_GROUP --location $RANDOM_REGION

Create the dev Azure Machine Learning workspace

az ml workspace create
--name $DEV_WORKSPACE_NAME
--resource-group $DEV_RESOURCE_GROUP
--location $RANDOM_REGION

Without this step, subsequent commands that configure the development workspace and create development data assets reference resources that have not yet been created.

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

Locate Lab 05 and the section containing Step 5 and Step 6. Insert the development resource group and Azure Machine Learning workspace commands between those steps, then verify that the later development workspace and data asset commands follow the new creation step.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, jupyter-notebook, shell
Domain
cloud, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.