Change podsecuritypolicy description from PREVIEW to DEPRECATING. #10175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Staging] Swagger Validation Report
️✔️ |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Azure CLI Extension Generation
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go
|
azure-sdk-for-java
|
azure-sdk-for-js
|
azure-sdk-for-net
|
azure-sdk-for-python
|
azure-sdk-for-python-track2
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
This was referenced Jul 16, 2020
|
Can one of the admins verify this patch? |
jluk
suggested changes
Jul 17, 2020
There was a problem hiding this comment.
small ask to clarify the description with more details
@palma21 / @robbiezhang FYI
...erservice/resource-manager/Microsoft.ContainerService/stable/2019-02-01/managedClusters.json
Outdated
Show resolved
Hide resolved
|
@nullmdr please take a look at this, AKS is deprecating a preview feature and we would like to signal a heads up via Swagger - we have already made public disclosure and direct email notifications for 90 days notice. Exposing this in details for swagger is an additional step to help customers get the message. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
gtxistxgao
approved these changes
Jul 18, 2020
jluk
approved these changes
Jul 19, 2020
|
hi @JunSun17 pls fix CI failure with instruction https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/ci-fix.md, then I'll merge the PR. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
yungezz
merged commit 85c0f5b
into
Azure:dev-containerservice-Microsoft.ContainerService-2020-07-01
PhoenixHe-NV
pushed a commit
that referenced
this pull request
Aug 19, 2020
* Adds base for updating Microsoft.ContainerService from version stable/2020-06-01 to version 2020-07-01 * Updates readme * Updates API version in new specs and examples * Add licenseType in WindowsProfile for AKS (#10050) * Change podsecuritypolicy description from PREVIEW to DEPRECATING. (#10175) * [AKS] Use POST operation for node image version (#10294) Co-authored-by: Xiaofang Zhang <xizha@microsoft.com> Co-authored-by: Chou Hu <abelch@microsoft.com> Co-authored-by: Jun Sun <33297523+JunSun17@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.