Skip to content

Network December release#4605

Closed
seyedfayaz wants to merge 44 commits intoAzure:december-network-releasefrom
seyedfayaz:network-november-release
Closed

Network December release#4605
seyedfayaz wants to merge 44 commits intoAzure:december-network-releasefrom
seyedfayaz:network-november-release

Conversation

@seyedfayaz
Copy link
Copy Markdown

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

MikhailTryakhov and others added 30 commits October 30, 2018 12:42
* Update specification/network/resource-manager/Microsoft.Network/stable/2018-08-01/networkWatcher.json

[Networkwatcher] add a new field "Format" with new type"FlowLogFormat" to FlowLogProperties

* Revert "Update specification/network/resource-manager/Microsoft.Network/stable/2018-08-01/networkWatcher.json"

This reverts commit f4f438a.

* Update specification/network/resource-manager/Microsoft.Network/stable/2018-10-01/networkWatcher.json

[networkwatcer] add FlowLogFormatParameters
* Adds base for updating Microsoft.Network from version stable/2018-08-01 to version 2018-10-01

* Updates readme

* Updates API version in new specs and examples

* Adds Rewrite rule set for Header CRUD

Adds the structure of rewriteRuleSets in the applicationGatewayProperties.
Adds recursively the sub structures in the rewriteRuleSet.
Adds the reference to rewriteRuleSet in the requestRoutingRule for both Basic rule and Path based rule.

* Adds examples for the Header CRUD in application gateway

* Fix the examples; replacing rules with rewriteRules.

* Fixing the properties of application Gateway rewriteRule

* Revert "Fixing the properties of application Gateway rewriteRule"

This reverts commit 05c9c91.

* Fixing the properties of application Gateway rewriteRule

* Mark the provisioning state as readOnly

* Mark etag as readOnly
…rces" (Azure#4467)

* Revert "Application Gateway - Adds Rewrite rule set for Header CRUD (Azure#4331)"

This reverts commit 633d12d.

* Revert "Port fix from PR 4459 to 2018-10-01 (Azure#4463)"

This reverts commit 5ea0c7b.

* Revert "change container nics property type on container nic config to resourceid (Azure#4459)"

This reverts commit baf31d9.
* identity and keyvault

* Capitalization comment
@sergey-shandar
Copy link
Copy Markdown
Contributor

@MikhailTryakhov is there anything else has to be addressed?

Copy link
Copy Markdown
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

@ravbhatnagar ravbhatnagar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple of minor notes. else looks fine

@nschonni
Copy link
Copy Markdown
Contributor

It looks like there was a bad merge somewhere and a bunch of files are being reverted and removed

@ravbhatnagar
Copy link
Copy Markdown
Contributor

Signing off from ARM side.

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMChangesRequested WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Dec 12, 2018
@hovsepm
Copy link
Copy Markdown
Contributor

hovsepm commented Dec 14, 2018

@seyedfayaz please rebase this PR and fix merge conflicts.

@MikhailTryakhov
Copy link
Copy Markdown
Contributor

@seyedfayaz you pushed us hard with all the team, but no actions visible now...

Copy link
Copy Markdown
Contributor

@jianghaolu jianghaolu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other reviews are not available until syntax issues are fixed. At this moment errors from other tools don't make sense.

"description": "The name of the DDoS custom policy."
},
{
"$ref": "./network.json#/parameters/ApiVersionParameter"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no 'network.json' under 2018-11-01 folder.

@@ -3,7 +3,7 @@
"info": {
"title": "NetworkManagementClient",
"description": "The Microsoft Azure Network management API provides a RESTful set of web services that interact with Microsoft Azure Networks service to manage your network resources. The API has entities that capture the relationship between an end user and the Microsoft Azure Networks service.",
"version": "2018-11-01"
"version": "2018-12-01"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this file be moved to 2018-12-01?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIK there is no 2018-12-01, the last NRP version this year is going to be 2018-11-01
@MikhailTryakhov please take a look

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay we have a 2018-12-01 folder and a bunch of specs with version=2018-12-01. They should be reverted to 2018-11-01?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jianghaolu @seyedfayaz @number213 of cause they should be reverted to 2018-11-01

@jianghaolu
Copy link
Copy Markdown
Contributor

Please reopen and target january-network-release.

@jianghaolu jianghaolu closed this Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.