-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add AzureFirewall swagger and examples #3276
Conversation
Automation for azure-sdk-for-nodeA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-javaA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
@ravbhatnagar new spec AzureFirewall. |
Hi @ravbhatnagar , @sergey-shandar , FYI we had gotten ARM approval when we prepared for private preview (https://github.com/Azure/azure-rest-api-specs-pr/pull/246) |
"properties":{ | ||
"privateIPAddress": { | ||
"type": "string", | ||
"description": "PrivateIPAddress of the network interface IP Configuration. This field is populated in the output." |
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.
This is actually the front end IP address of the Internal Loadbalancer. we can check with Yair on how to expose this and if we should say this is the IPAddress they need to set as nexthop in UDR.
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.
Spoke with Yair, we will use the following description: The Firewall Internal Load Balancer IP to be used as the next hop in User Defined Routes
"format":"int32", | ||
"maximum":65000, | ||
"exclusiveMaximum":false, | ||
"minimum":0, |
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.
We start priority from 101. 0 - 100 and > 6500 is reserved
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.
In NRP looks like user can start from 100. Will update the minimum to reflect that. Thanks for catching
@MikhailTryakhov |
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.
LGTM. It's a new feature, Samer approved to push it to master directly.
Please merge Network-2018-06-01 first and this one after
}, | ||
"description":"Collection of rules used by a network rule collection." | ||
}, | ||
"provisioningState":{ |
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.
We only care about provisioning state on AzureFirewallProperties why do we have to mentioned provisioning state on these child resources? we don't have operations on them. Also the same is for Ipconfig as well.
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.
I see that other resources have it and NRP returns this value. So you can ignore this comment.
@joannakleong follow @MikhailTryakhov advise and then let me know when it can be merged. |
@sergey-shandar This is good to merge |
Thanks everyone for the prompt review! @sergey-shandar Before merging, I'd like to resolve @MadhusudhanRavi comments on the description fields for a couple properties |
@sergey-shandar Pushed a final commit. Can this swagger be merged next Tuesday? |
@sergey-shandar This good to merge. The dependent PR here has been merged |
I spoke with @lmazuel, it's a timeout issue. |
@joannakleong Could you send me a link to ARM approval? This link https://github.com/Azure/azure-rest-api-specs-pr/pull/246 has no AzureFirewall. |
@sergey-shandar yes, this is because for private preview we named ourselves "Secure Gateway" and now we've finalized the name "Azure Firewall" |
@AutorestCI rebuild azure-sdk-for-python |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger