-
Notifications
You must be signed in to change notification settings - Fork 4.1k
PS Release Microsoft.Network 2024-10-01 #28558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
… in template for application Gateway Backend Settings (#28000) Co-authored-by: Rajat Gupta <rajatgup@microsoft.com>
…abledRules Property (#28035) Co-authored-by: yoavmalichi_microsoft <yoavmalichi@microsoft.com>
…wallPolicyWithCustomBlockResponse
Co-authored-by: Karthik Gumpu (from Dev Box) <karthikgumpu@microsoft.com>
Co-authored-by: Prajjwal Kamboj <pkamboj@microsoft.com>
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Azure PowerShell Network module to version 2024-10-01, introducing new functionality for Network Security Perimeter service tags and Application Gateway backend HTTP settings enhancements.
- Added a new cmdlet
Get-AzNetworkSecurityPerimeterServiceTag
for retrieving supported service tags - Enhanced Application Gateway backend HTTP settings with new SSL/TLS validation properties
- Updated API specifications from 2024-07-01 to 2024-10-01
Reviewed Changes
Copilot reviewed 19 out of 254 changed files in this pull request and generated 2 comments.
Show a summary per file
File | Description |
---|---|
tools/StaticAnalysis/Exceptions/Az.KeyVault/ExampleIssues.csv | Added static analysis exception for Install-Module cmdlet |
src/Network/NetworkSecurityPerimeter.Autorest/ (multiple files) | Added new cmdlet and documentation for NetworkSecurityPerimeter ServiceTags |
src/Network/Network/help/ (multiple files) | Updated help documentation for Application Gateway cmdlets with new SSL/TLS parameters |
src/Network/Network/Models/PSApplicationGatewayBackendHttpSettings.cs | Added new properties for SSL/TLS validation and dedicated connections |
src/Network/Network/ApplicationGateway/BackendHttpSettings/AzureApplicationGatewayBackendHttpSettingsBase.cs | Implemented new SSL/TLS validation parameters in backend HTTP settings |
src/Network/Network/ChangeLog.md | Updated changelog with new features |
src/Network/Network/Az.Network.psd1 | Added new cmdlet to exports and updated module metadata |
src/Network/Network.Management.Sdk/README.md | Updated API version references from 2024-07-01 to 2024-10-01 |
src/Network/Network.sln | Updated project GUID for NetworkSecurityPerimeter.Autorest |
[-DedicatedBackendConnection <Boolean>] [-ValidateCertChainAndExpiry <Boolean>] | ||
[-ValidateSNI <Boolean>] | ||
[-SniName <String>] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The line breaks in the syntax section are inconsistent. Line 23 has parameters on the same line, while lines 24-25 have single parameters. Consider reformatting for consistency, either putting all new parameters on one line or giving each parameter its own line.
[-DedicatedBackendConnection <Boolean>] [-ValidateCertChainAndExpiry <Boolean>] | |
[-ValidateSNI <Boolean>] | |
[-SniName <String>] | |
[-DedicatedBackendConnection <Boolean>] | |
[-ValidateCertChainAndExpiry <Boolean>] | |
[-ValidateSNI <Boolean>] | |
[-SniName <String>] |
Copilot uses AI. Check for mistakes.
@@ -20,6 +20,9 @@ New-AzApplicationGatewayBackendHttpSetting -Name <String> -Port <Int32> -Protoco | |||
[-AuthenticationCertificates <PSApplicationGatewayAuthenticationCertificate[]>] | |||
[-TrustedRootCertificate <PSApplicationGatewayTrustedRootCertificate[]>] [-PickHostNameFromBackendAddress] | |||
[-HostName <String>] [-AffinityCookieName <String>] [-Path <String>] | |||
[-DedicatedBackendConnection <Boolean>] [-ValidateCertChainAndExpiry <Boolean>] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The line breaks in the syntax section are inconsistent. Line 23 has parameters on the same line, while lines 24-25 have single parameters. Consider reformatting for consistency, either putting all new parameters on one line or giving each parameter its own line.
[-DedicatedBackendConnection <Boolean>] [-ValidateCertChainAndExpiry <Boolean>] | |
[-DedicatedBackendConnection <Boolean>] | |
[-ValidateCertChainAndExpiry <Boolean>] |
Copilot uses AI. Check for mistakes.
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
|
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.