-
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
Added optional PublicNetworkAccess to server properties #8421
Conversation
Pull from Azure-rest-api-specs for latest changes
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-python - Release
|
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -420,6 +420,18 @@ | |||
"minimalTlsVersion": { | |||
"description": "Minimal TLS version. Allowed values: '1.0', '1.1', '1.2'", | |||
"type": "string" | |||
}, | |||
"publicNetworkAccess": { | |||
"description": "Whether or not public endpoint access is allowed for this server. Value is optional but if passed in, must be 'Enabled' or 'Disabled'", |
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.
Value is optional but if passed in, must be 'Enabled' or 'Disabled'
I think that documentation explaining this will be automatically written (when generating SDKs) based on the x-ms-enum property. However, I think that what "public endpoint access" is might not be sufficiently obvious to somebody who doesn't have context.
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.
OK I can discuss with Rohit as to what is better documentation for this after this round is merged in first
@zikalino Do you know why sdk automation failure is occurring? Its failing on permissions denied |
Azure Pipelines successfully started running 1 pipeline(s). |
sdk failure unrelated |
* Add PublicNetworkAccess option to server properties * Remove IdentityTypeWithNone unrelated changes to prevent test breaking * Remove None from enum type - unrelated changes to prevent test breaking * Prettify swagger file
Latest improvements:
We are adding an optional boolean property, PublicNetworkAccess, to the Server ARM Api. This is used to determine whether we allow public endpoints to connect to databases under this server or not.
This was already signed off in azure-rest-api-specs-pr:
https://github.com/Azure/azure-rest-api-specs-pr/pull/1083
Note: We have some deadlines to hit so if we could get quick signoff on this, that would be great :)
Contribution checklist:
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.