-
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
Update to Release 3.5 standard (pre GA) #5370
Conversation
NFSAAS-1505 minor update and validation fixes
Put (and patch) for snapshots. Service level definition changes.
NFSAAS-1505 bring in line with RP
NFSAAS-1505 correct resource reference and limits
Incorrect pool resource reference Name elements of property not required Correction to return status code
NFSAAS-1505 resource and property changes
NFSAAS-1505 status codes
NFSAAS-1505 tidy up examples
NFSAAS-1505 tidy up examples
NFSAAS-1644 remove mt get and add put status code
NFSAAS-1644 remove mt get add status for put
NFSAAS-1875 update to R3.5 standard
Can one of the admins verify this patch? |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsA 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-nodeNothing to generate for azure-sdk-for-node |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-netA PR has been created for you: |
REST Spec PR 'Azure/azure-rest-api-specs#5370' REST Spec PR Author 'leonardbf' REST Spec PR Last commit
* NFSAAS-1875 Update to R3.5 Standard * NFSAAS-1875 update to R3.5 standard
REST Spec PR 'Azure/azure-rest-api-specs#5370' REST Spec PR Author 'leonardbf' REST Spec PR Last commit
@kpajdzik would you take this one? thanks! |
@veronicagg I will :) |
"properties": { | ||
"activeDirectoryId": { | ||
"type": "string", | ||
"description": "Id of the active drectory" |
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.
drectory -> directory
Maybe also capitalize too
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.
Fixed
}, | ||
"status": { | ||
"type": "string", | ||
"description": "Status of the active drectory" |
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.
drectory -> directory
Maybe also capitalize too
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.
Fixed
}, | ||
"allowedClients": { | ||
"type": "string", | ||
"description": "Client ingress specification as comma seperated string with IPv4 CIDRs, IPv4 host addresses and host names" |
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.
seperated -> separated
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.
Fixed
@@ -1627,6 +1771,12 @@ | |||
"type": "string", | |||
"example": "255.255.255.0" | |||
}, | |||
"smbServerFqdn": { | |||
"title": "smbServerFQDN", | |||
"description": "The SMB server's Fully Qualified Doman Name, FQDN", |
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.
Doman -> Domain
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.
Fixed
* NFSAAS-1875 Update to R3.5 Standard * NFSAAS-1875 update to R3.5 standard * NFSAAS-1875 updated from review comments
REST Spec PR 'Azure/azure-rest-api-specs#5370' REST Spec PR Author 'leonardbf' REST Spec PR Last commit
Merging to fork from azure master
If you haven't taken a look at our new onboarding experience at OpenAPIHub, it's a convenient way to create your PR when you're copying from an existing API version or when you're editing your existing specs. If you have any feedback or questions, feel free to use the feedback button on top of the site for help. Thanks! |
@anuchandy Could you please take a look? |
"type": "string", | ||
"description": "Username of Active Directory domain administrator" | ||
}, | ||
"password": { |
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.
Could you elaborate on this parameter? Is this secure?
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.
It's credentials for the AD admin at the lower level. The RP only passes this through to the lower level. It is transmitted via https to the RP. But yes quite correct, the security is in question and there is an internal ticket to address this for the next release (pre-GA). Of course this swagger only reflects this implementation.
"type": "boolean", | ||
"description": "Read only access" | ||
}, | ||
"unixReadWrite": { |
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.
Why is it prefixed with "unix"? Should this be included in description 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.
It's a consequence of a lower level API that the RP calls. This value is simply passed through. But it is because it only applies to the NFS permissions. It doesn’t do anything useful for NTFS.
Just a clarification - is Java SDK something that Microsoft will auto generate? Is it one of those handled from within the Devx OpenAPI hub for instance? |
Yes, it is the one handled by OpenAPI portal. It included Java, Node.js (soon deprecated so no new SDKs), TypeScript, Ruby and Python. |
I've provided answers for the comments but this PR is still open. Can someone either respond if there are further issues or merge please. |
Since this is approved, is there any chance it could be merged? Thanks. |
Still in preview - breaking changes are not considered applicable.
Changes:
(internal ticket NFSAAS-1875)
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:
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.