Network May release #9786
Merged
Network May release #9786
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…01 to version 2020-05-01
…ualApplianceSites child resources (#9357) * Adds base for updating Microsoft.Network from version stable/2020-03-01 to version 2020-05-01 * Updates readme * Updates API version in new specs and examples * Final changes * Fix formatting issues * Fix merge and formatting issues * Fix formatiing * Ipconfig properties * Fix build errors * Lint check * Fix semantics errors * Address review comments * Fix prettier and nextLink checks * Fix dots * Address errors * Fix Ipconfig version Co-authored-by: dexiang-ms <64503627+dexiang-ms@users.noreply.github.com>
* Adding DnsProxySettings Support in Firewall Policy dnsServers, dnsEnableProxy, dnsRequireProxyForNetworkRules are added as subproperties. * spell check * Removing DNS as prefix on sub properties. * Syntax error. * DnsProxySettings to DNSSettings * Fixing proxy settings name. Co-authored-by: Ishani Gupta <isgu@microsoft.com>
* Added new properties to ConnectivityHop * Fixed spelling * added x-ms-client-flatten to HopLink.properties.properties
#9356) * Rename Firewall Policy child resource RuleGroup to RuleCollectionGroup * rebase with ti whitelist * rebase with ti whitelist * rebase with ti whitelist * prettier run * making nat rule into a collection * prettier run
* multi pip for firewall in hub swagger change * resolving issues
1. Exposed direct PUT/DELETE APIs for hubvnet connections. This is the API expected to be used in the future by all consumers (direct rest api calls, powershell, portal, azure cli). This avoids needing a put on the virtual hub every time a hubvnet connection is to be added/changed. 2. Deprecate specifying hubvnet connection in virtualHub PUT. This is to avoid having multiple APIs to do the same thing. Also having this API introduces other complexities and breaks some scenarios. 3. Deprecate allowHubToRemoteVnetTransit and allowRemoteVnetToUseHubVnetGateways flags in hubvnet connection. These flags are maintained internally in the implementation and shouldn't be exposed to the user. For now, just mark it as such. Will be removed in later release. Co-authored-by: Shyam Dharmarajan <shdharma@microsoft.com>
* v1 * making boolean as nullable Co-authored-by: Ishani Gupta <isgu@microsoft.com>
* Add Routing State and expose Effective Routes Api * updated opId name and added examples * prettier fix done * rename variable to prevent conflict
* Updating VpnGateway examples * prettier Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com>
* Application Gateway Private Link Support * Fix comments * Fix comments for including example
[Staging] Swagger Validation Report️~[Staging] BreakingChange [Detail]Posted by Swagger Pipeline |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@myronfanqiu could you please review & merge? This is a monthly release for Network |
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go - Release
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-java - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-js - Release
|
|
Can one of the admins verify this patch? |
|
@number213 Please fix LintDiff CI. Thanks. |
mmyyrroonn
approved these changes
Jun 9, 2020
|
@myronfanqiu done in #9787, please approve and merge |
openapi-assignment-bot
bot
added
the
WaitForARMFeedback
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Merged this PR since all changes have been reviewed by ARM team. |
mmyyrroonn
reviewed
Jun 12, 2020
| @@ -59,6 +60,7 @@ batch: | |||
| ```yaml $(multiapi) && $(track2) | |||
| clear-output-folder: true | |||
| batch: | |||
| - tag: package-2020-04 | |||
There was a problem hiding this comment.
@number213 We don't add package-2020-05 into this one
00Kai0
pushed a commit
to 00Kai0/azure-rest-api-specs
that referenced
this pull request
Oct 12, 2020
* Adds base for updating Microsoft.Network from version stable/2020-04-01 to version 2020-05-01 * Updates readme * Updates API version in new specs and examples * Add VirtualHubBgpConnections, VirtualHubIpConfigurations, NetworkVirtualApplianceSites child resources (Azure#9357) * Adds base for updating Microsoft.Network from version stable/2020-03-01 to version 2020-05-01 * Updates readme * Updates API version in new specs and examples * Final changes * Fix formatting issues * Fix merge and formatting issues * Fix formatiing * Ipconfig properties * Fix build errors * Lint check * Fix semantics errors * Address review comments * Fix prettier and nextLink checks * Fix dots * Address errors * Fix Ipconfig version Co-authored-by: dexiang-ms <64503627+dexiang-ms@users.noreply.github.com> * Change NRP repo for validation scripts (Azure#9394) * Move terminateTLS flag to ApplicationRuleCondition (Azure#9539) * DNS Proxy support for Firewall Policy (Azure#9461) * Adding DnsProxySettings Support in Firewall Policy dnsServers, dnsEnableProxy, dnsRequireProxyForNetworkRules are added as subproperties. * spell check * Removing DNS as prefix on sub properties. * Syntax error. * DnsProxySettings to DNSSettings * Fixing proxy settings name. Co-authored-by: Ishani Gupta <isgu@microsoft.com> * fix network (Azure#9369) (Azure#9547) * fix network * duplicated publicipprefix * fixed example in 2018-01-01 * final updates * missing examples (cherry picked from commit 42d9639) * Added new properties to ConnectivityHop (Azure#9386) * Added new properties to ConnectivityHop * Fixed spelling * added x-ms-client-flatten to HopLink.properties.properties * Rename Firewall Policy child resource RuleGroup to RuleCollectionGroup (Azure#9356) * Rename Firewall Policy child resource RuleGroup to RuleCollectionGroup * rebase with ti whitelist * rebase with ti whitelist * rebase with ti whitelist * prettier run * making nat rule into a collection * prettier run * Multiple Public IPs support for Azure Firewall in Virtual Hub (Azure#9560) * multi pip for firewall in hub swagger change * resolving issues * VirtualWan: Hubvnet Connection related changes (Azure#9536) 1. Exposed direct PUT/DELETE APIs for hubvnet connections. This is the API expected to be used in the future by all consumers (direct rest api calls, powershell, portal, azure cli). This avoids needing a put on the virtual hub every time a hubvnet connection is to be added/changed. 2. Deprecate specifying hubvnet connection in virtualHub PUT. This is to avoid having multiple APIs to do the same thing. Also having this API introduces other complexities and breaks some scenarios. 3. Deprecate allowHubToRemoteVnetTransit and allowRemoteVnetToUseHubVnetGateways flags in hubvnet connection. These flags are maintained internally in the implementation and shouldn't be exposed to the user. For now, just mark it as such. Will be removed in later release. Co-authored-by: Shyam Dharmarajan <shdharma@microsoft.com> * Destination FQDNs in FirewallPolicy for network rules. (Azure#9609) * v1 * making boolean as nullable Co-authored-by: Ishani Gupta <isgu@microsoft.com> * VirtualHub : Add Routing State and expose Effective Routes Api (Azure#9385) * Add Routing State and expose Effective Routes Api * updated opId name and added examples * prettier fix done * rename variable to prevent conflict * Updating VpnGateway examples for bgpSettings (Azure#9656) * Updating VpnGateway examples * prettier Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com> * Application Gateway Private Link Support (Azure#9490) * Application Gateway Private Link Support * Fix comments * Fix comments for including example * Add nvaSku property for NetworkVirtualAppliance (Azure#9682) * code fixes for hubIPAddresses (Azure#9775) * Fix lint errors (Azure#9787) Co-authored-by: naveenchekuri <nachekur@microsoft.com> Co-authored-by: dexiang-ms <64503627+dexiang-ms@users.noreply.github.com> Co-authored-by: odedlaz <odedlaz@users.noreply.github.com> Co-authored-by: Ishani Gupta <ishani.gupta27.ig@gmail.com> Co-authored-by: Ishani Gupta <isgu@microsoft.com> Co-authored-by: Zim Kalinowski <zikalino@microsoft.com> Co-authored-by: irrogozh <irrogozh@microsoft.com> Co-authored-by: Sai Sujith Reddy Mankala <samankal@microsoft.com> Co-authored-by: Anchal Kapoor <anchalka@usc.edu> Co-authored-by: shyamshd <64368451+shyamshd@users.noreply.github.com> Co-authored-by: Shyam Dharmarajan <shdharma@microsoft.com> Co-authored-by: Ritvika Reddy Nagula <rinagula@microsoft.com> Co-authored-by: Khushboo Baheti <37917868+Khushboo-Baheti@users.noreply.github.com> Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com> Co-authored-by: jaishals <jaishal.shah@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.