[Doc]: Add-AzApplicationGatewaySslCertificate example omits required Set-AzApplicationGateway to persist changes
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- azure, powershell
- Domain
- documentation
Research direction
Open src/Network/Network/help/Add-AzApplicationGatewaySslCertificate.md and review the existing example for the certificate workflow. Add the required persistence step using Set-AzApplicationGateway -ApplicationGateway $AppGW, then verify the rendered example clearly shows that the change is saved to Azure.
Written by the indexing model from the issue text.
Description
Type of issue
Other (describe below)
Feedback
The current example shows how to add an SSL certificate to an Application Gateway by updating the in-memory object returned by Get-AzApplicationGateway and then calling Add-AzApplicationGatewaySslCertificate. However, it does not demonstrate the final step needed to persist those changes back to the Azure resource.
Without calling Set-AzApplicationGateway -ApplicationGateway $AppGW (or Update-AzApplicationGateway in some patterns), users may assume the change is applied, but the certificate is not actually pushed to the Application Gateway.
# Persist the change to Azure (required)
Set-AzApplicationGateway -ApplicationGateway $AppGW
Page URL
Content source URL
Author
@mikefrobbins
Document Id
d9014bc0-dbaa-ad6f-bb29-f30fe3c2a3bd
Platform Id
805a1f56-1b93-78c3-7724-9427da6332a5
- 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 ·