-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Dev containerservice microsoft.container service 2019 02 01 #5399
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
Dev containerservice microsoft.container service 2019 02 01 #5399
Conversation
…w/2018-08-01-preview to version 2019-02-01
…5156) * including orchestratorVersion and provisioning state for agent pool * fixing the readme.go.md * including enablePodSecurityPoliy properties for managedcluster and updating examples * fixing the example for enablePodSecurityPolicy
* including apiServerAuthorizedIPRanges * support azure network policy
* mark the new features as PREVIEW * mark vmss as required for az
* copy 2018-08-01-preview folder to 2019-02-01 without changes * implementing agentpool api in 2019-02-01 * fixing minor api-version errors * fixing the agentpool list operation paths * fixing the agentpool example * add default response * including name validation
Automation for azure-sdk-for-jsA PR has been created for you: |
Automation for azure-sdk-for-pythonA PR has been created for you: |
Automation for azure-sdk-for-rubyA PR has been created for you: |
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-nodeA PR has been created for you: |
Automation for azure-sdk-for-javaA PR has been created for you: |
Automation for azure-sdk-for-goA PR has been created for you: |
|
@praries880, please let me know the correct process to solve the merge conflict. I don't have write permission to Azure: dev-containerservice-Microsoft.ContainerService-2019-02-01 branch so not sure how to solve the conflict. So I did the merge and solved the conflict in my private repo xizhamsft: dev-containerservice-Microsoft.ContainerService-2019-02-01 and then sent out a new PR to merge xizhamsft: dev-containerservice-Microsoft.ContainerService-2019-02-01 ->Azure: dev-containerservice-Microsoft.ContainerService-2019-02-01 in PR:#5402 Hopefully once 5402 is merged, 5399 will be updated automatically without the merge conflict Please let me know if I am doing this the correct way, we need this merged ASAP |
|
will try again. |
Merge Agent pool API from dev branch to master
The change is already approved in this PR:
#5352
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.