[Doc]: Update-AzGallery -Tenant has incorrect documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- azure, powershell
- Domain
- cloud, documentation
Research direction
Start at the linked Update-AzGallery Learn page and inspect the -Tenant example. Compare the documented comma-separated value with the working PowerShell string[] example provided in the issue. Done means the page accurately documents syntax that works for multiple tenant IDs.
Written by the indexing model from the issue text.
Description
Type of issue
Code doesn't work
Feedback
https://learn.microsoft.com/en-us/powershell/module/az.compute/update-azgallery?view=azps-15.4.0
this example shows
Update-AzGallery -ResourceGroupName $rgname -Name $galleryName -Permission Groups -Share -Tenant xxxxxxxx-xxx-xxxxxxx,zzzzzz-zzzzzzz-zzzzzz
that tenantIds should be comma separated values, but it doesn't work like it shows
I have got it to work by passing a string[]
for example
$tenantIds = @( 'xxxxxxxx-xxx-xxxxxxx'; 'zzzzzz-zzzzzzz-zzzzzz')
Update-AzGallery -ResourceGroupName $rgname -Name $galleryName -Permission Groups -Share -Tenant $tenantIds
works, but
$tenantIds = @( 'xxxxxxxx-xxx-xxxxxxx'; 'zzzzzz-zzzzzzz-zzzzzz')
Update-AzGallery -ResourceGroupName $rgname -Name $galleryName -Permission Groups -Share -Tenant $($tenantIds -join ',')
doesn't work
Page URL
https://learn.microsoft.com/en-us/powershell/module/az.compute/update-azgallery?view=azps-15.4.0
Content source URL
No response
Author
No response
Document Id
No response
Platform Id
No response
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 49
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.
More from Azure/azure-powershell
-
[Feature]: Opencustomer-reported feature-request needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-powershell#30135 ·
-
customer-reported feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Azure/azure-powershell#30100 ·
-
Get-AzCognitiveServicesModelCapacity does not support querying models with the Format "Mistral AI" Openbug customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Azure/azure-powershell#29632 · 1 reaction ·
-
bug customer-reported needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Azure/azure-powershell#29615 ·
-
bug customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/azure-powershell#29540 · 1 comment · 2 reactions ·
All issues in Azure/azure-powershell
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·