-
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 client tsp for AzureFleet #30238
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Generated ApiView
|
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Updated with the template. |
@ArthurMa1978 - Thank-you! You also need to fill out the intake form in order for the repo and reviewers to handle your PR properly. Please fill out both the Purpose of this PR and Due diligence checklist sections. |
Updated. |
@live1206 Can you also verify that these changes don't break other sdks? Or would we need another release for Go and Python sdk? |
Hi @raych1, please approve |
Why do we even have SDK breaking change for beta versions and there is no GA version released yet? |
@raych1 Why is sdk-suppressions.yaml not parsed for Python? https://github.com/Azure/azure-rest-api-specs/pull/30238/checks?check_run_id=29144749206 |
We don't have a GA version yet. |
Azure/azure-sdk-tools#8862 Not supported yet so we have to add approval label directly. |
* Add client tsp for AzureFleet * update * Update examples with valid url to fix model validation failures * Create sdk-suppressions.yaml * update sdk-suppressions.yaml --------- Co-authored-by: Sahil Arora <arorasahil@microsoft.com> Co-authored-by: Wei Hu <live1206@gmail.com> Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com> Co-authored-by: Alancere <804873052@qq.com>
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.