Skip to content

feat(gallery): add azure-network-manager-demo scenario#105

Draft
petender wants to merge 1 commit into
MicrosoftLearning:mainfrom
petender:contribute/azure-network-manager-demo
Draft

feat(gallery): add azure-network-manager-demo scenario#105
petender wants to merge 1 commit into
MicrosoftLearning:mainfrom
petender:contribute/azure-network-manager-demo

Conversation

@petender

Copy link
Copy Markdown
Collaborator

New Template Registration

Field Value
Scenario azure-network-manager-demo
Repo petender/tdd-azd-azure-network-manager-demo
Tags az-700,az-104,msft,vnets,bastion,virtualmachine,loganalytics
Sample App No
Demo Guide Yes
Contributor @petender

Tag Validation

All tags validated against src/data/tags.tsx TagType union: ✅ PASSED

Deployment

gh repo clone petender/tdd-azd-azure-network-manager-demo cd tdd-azd-azure-network-manager-demo azd init azd up

@rob-foulkrod

Copy link
Copy Markdown
Collaborator

While validating this template, I noticed the README says azd up will prompt for the VM admin username/password. In practice, the template reads these values from environment variables:

  • AZURE_VM_ADMIN_USERNAME
  • AZURE_VM_ADMIN_PASSWORD

I tested with a clean .azure environment and no cached values; azd up did not prompt for the missing password and proceeded until Azure failed with osProfile.adminPassword missing/null.

Validation succeeded after setting the variables manually, but environment variables are not the common/expected path for trainers using this catalog. Prompting during azd up would be the preferred experience here, matching the README.

Could you either wire these as prompted azd inputs, or update the deployment instructions clearly if env vars must remain required?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants