microsoft / microsoft/virtualnodesOnAzureContainerInstances
Onboarding instructions are too portal driven
Open
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 12
- Forks
- 11
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 7
Description
ClientId Location Name PrincipalId ResourceGroup TenantId
------------------------------------ ---------- ------------- ------------------------------------ ----------------------- ------------------------------------
bbd92693-0cca-44b8-a7d5-4cbf8a5b7c9e westus3 vk2-agentpool fba63fbf-bc5d-412a-b4e3-e9d29a5681cc MC_paultest_vk2_westus3 72f988bf-86f1-41af-91ab-2d7cd011db47
and then
az role assignment create \
--assignee fba63fbf-bc5d-412a-b4e3-e9d29a5681cc \
--role "Contributor" \
--scope /subscriptions/$(az account show --query id -o tsv)/resourceGroups/MC_paultest_vk2_westus3
For example.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Find the onboarding instructions containing the shown az identity list and az role assignment create commands. Review how the current steps depend on portal-driven actions, then update the instructions so the onboarding flow clearly explains the command-line approach and its expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100