-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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 new OsType parameters for Microsoft.Web/availablestacks #3808
Conversation
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-goNothing to generate for azure-sdk-for-go |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
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 get nervous about extending enum values inside of API Versions for the following reasons:
- API Versions expose a mechanism for reasoning about availability between regions.
- While this type already looks to be modeled as a string, applications will need to be retooled to expose/reason about the new options. Without changing API Version, it is hard to build tooling to identify places where the enum list has been updated.
That said, I don't think those grounds are enough to block this or any other individual PR. However, I want to make sure that this conversation is included when considering what changes warrant waiting for an API Version boundary. Better yet, trying to change the culture to one where deploying new API Versions is a lighter-weight, more common operation.
Looks good. Signing off from ARM side. Just one minor note - Currently in the response body, i couldnt find a way to know which stack is for Linux or Windows. How do you differentiate that looking at the response. Specially when the filter query parameter is optional so by default in the response both stacks can be present. |
The response body will include the type based on the ostype query parameter. if the query parameter is skipped it is implicitly assumed to be Windows and only Windows stacks will be returned. |
Are there any more concerns? Can we merge this PR? |
Talked offline with @naveedaz, merging now. |
No description provided.