-
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
Adding June Swagger Update - Azure Container Instance #3170
Conversation
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-libraries-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Hi @samkreter ! |
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.
Mind updating the Golang config in the README as well? https://github.com/Azure/azure-rest-api-specs/pull/3170/files#diff-5c3d140eca9525738ed2ab683fb322afR155
…rest-api-specs into sakreter-JuneAPISwagger
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.
Now we're just waiting for @ravbhatnagar
}, | ||
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerInstance/containerGroups/{containerGroupName}/containers/{containerName}/logs": { | ||
"get": { | ||
"operationId": "ContainerLogs_List", |
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.
There are some semantics that we introduce to OperationIDs in AutoRest. Chiefly, we use the prefix here to denote an "operation group". For some languages, each operation group gets is own Client type.
For that reason, I'd recommend having fewer Operation Groups:
ContainerGroupUsage_List
-> ContainerGroups_ListUsage
ContainerLogs_List
-> Container_ListLogs
StartContainer_LaunchExec
-> Container_StartExecLaunch
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 took another look and found another thing we may want to tweak, not necessary to fix it though! Just acknowledge if you don't want to fix it. :)
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.
@marstr I would rather save those for the next PR so we can get this June release out. I can update those changes quickly for another PR.
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'd be a breaking change in the future, so we should do it now or never. Your choice though. :)
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.
When comparing the two API Versions against one another, this is actually a relatively small change. Nothing troublesome jumped out to me.
edit: wrong window, though the approval counts.
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