-
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
Microsoft.ContainerService API Version 2020-02-01 #8388
Microsoft.ContainerService API Version 2020-02-01 #8388
Conversation
…/2020-01-01 to version 2020-02-01
* Spot Pool Change * type has to be number * ref example
* Add properties for networkMode * rm the empty enum
* add autoScalerProfile to spec * add example for put MC * add to custom words * add list of accepted params * disable linting for profile * update example
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-js - Release
|
@gtxistxgao could you give a detailed list about what's this version change compared to |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -0,0 +1,84 @@ | |||
{ |
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.
new parameters are added into a new file( AgentPoolsCreate_Spot.json
) other than AgentPoolsCreate_Update.json
, I am not sure whether this is the right way.
@zikalino could you take a look? Thanks.
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 reviewed earlier. #8342
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 just the example spec and its linked to here
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
} | ||
} | ||
}, | ||
"x-ms-long-running-operation": true, |
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.
just confirm, updating tag is long running operation either.
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 doesn't seems to be a long running operation. But this value is not related to the changes happens in this API version and is the same with previous version 2020-01-01 as it is copied automatically by OpenAPI.
"description": "(PREVIEW) Whether to enable Kubernetes Pod security policy." | ||
}, | ||
"networkProfile": { | ||
"$ref": "#/definitions/ |
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.
scan-interval [](start = 13, length = 13)
I discussed this on another PR. Generally the naming convention is lowerCaseCamelCase for property names, but since these are passed through to a Kubernetes extension, I think there's value in keeping them as-is. Otherwise, the users will have to create a mental mapping between scanInterval
becoming scan-interval
and some for all others.
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.
Yup, for instance the Python SDK would show it as "scanInterval" in the GET MC response. But for serializing and deserializing, they'd do the conversion to/from "scan-interval" properly. I think it's a tradeoff here to achieve recognizable parameters.
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.
Signed off from ARM side.
HI @marwanad is the PR ready to merge? that means, service change is on Prod already. thanks. |
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.