-
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
[Service Fabric Managed Clusters] 2021-01-01-preview #12639
[Service Fabric Managed Clusters] 2021-01-01-preview #12639
Conversation
Hi, @a-santamaria Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Swagger Validation Report
|
Hi, @a-santamaria your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @ |
Swagger Generation Artifacts
|
Rule | Message |
---|---|
RestBuild error |
"logUrl":"https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=192574&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b", "detail":"Run.ps1 failed with exit code 1 " |
Hi @a-santamaria, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi, @a-santamaria your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @ChenTanyi |
...eFabricManagedClusters/preview/2021-01-01-preview/examples/NodeTypeGetOperation_example.json
Outdated
Show resolved
Hide resolved
...agedClusters/preview/2021-01-01-preview/examples/ManagedClusterVersionsListByOS_example.json
Outdated
Show resolved
Hide resolved
...FabricManagedClusters/preview/2021-01-01-preview/examples/NodeTypeListOperation_example.json
Outdated
Show resolved
Hide resolved
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.
A few comments. Up to @ChenTanyi how they feel about splitting out APIs that exist in the service fabric SDK to another SDK
...anager/Microsoft.ServiceFabricManagedClusters/preview/2021-01-01-preview/managedcluster.json
Show resolved
Hide resolved
...er/Microsoft.ServiceFabricManagedClusters/preview/2021-01-01-preview/managedapplication.json
Show resolved
Hide resolved
...er/Microsoft.ServiceFabricManagedClusters/preview/2021-01-01-preview/managedapplication.json
Outdated
Show resolved
Hide resolved
@akning-ms @josefree @PhoenixHe-msft @jianyexi Would you take a look at it? |
@ChenTanyi I can't figure out what is the issue with the python SDK generation, can you help, please? |
@msyyc @PhoenixHe-msft Could you take a look at the python generation error? |
...anagedClusters/preview/2021-01-01-preview/examples/ManagedClusterPatchOperation_example.json
Show resolved
Hide resolved
@msyyc @PhoenixHe-msft did you get a chance to look at the issue? I don't think its related to the changes its saying that it can't find bundle:
|
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
@ChenTanyi I fixed the issue with the python sdk generation and it's signed off by ARM. Can we merge the pr? |
* add servicefabricmanagedclusters folder with 2020-01-01-preview specs * update swagger with version 2021-01-01-preview * fix validation errors * add required systemData param in resources and add missing formats * fix formats * add ipv4Address, fix clusterCertificateThumbprints and descriptions * fix patch (only tags), remvoe clusterVersions, fix nsg * remove unnecessary example * fix patch descriptions and full arm resource id for type version * fix sdk profile name * fix lastModifiedAt description and python sdk path * add missing applicationTypeVersionsCleanupPolicy * fix location description and app example params * remove after_scripts for python sdk Co-authored-by: Alfredo Santamaria Gomez <alsantam@microsoft.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
We already had a previous APIversion for managed clusters here: 2020-01-01-preview But we want to move it to its own swagger folder so we can manage APIs and SDKs independently and not face conflicts with models.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
Target Date for new api version: 2/8/2021
2/5/2021
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.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
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.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.