-
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
Update redisenterprise readme files for C#, Azure CLI, and Azure Resource Manager Schema #12943
Update redisenterprise readme files for C#, Azure CLI, and Azure Resource Manager Schema #12943
Conversation
Hi, @greenms 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. [email protected] |
Swagger Validation Report
|
Swagger Generation Artifacts
|
@greenms Can merge once the checks pass |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
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 except maybe the TLS enum question
@markcowl I don't understand the way azure-cli-extensions and azure-sdk-for-python-track2 are failing, any insights? |
Thanks Tim. I also just sent out email requests for help on the Python Track2 failure (sent to @jsntcy and Yuchao Yan) and the Azure CLI failure (sent to @achandmsft and [email protected]) |
Identified an issue in the setup instructions for Azure CLI: Azure/autorest.az#744 |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
@markcowl @ArcturusZhang I believe I verified that without any of these readme file changes, the Python Track2 code generation will still fail with the 'pass-thru' TypeError message. You can see in this Draft PR that I introduce some harmless whitespace to trigger the SDK automation pipeline to run, and that the Python Track2 code gen fails with the same error: #12962 Can I please get this PR merged even with the failing check, due to it not being caused by anything I'm changing in this PR? Thanks. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Hi @greenms, Your PR has some issues. Please fix the CI sequentially by following the order of
|
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
The latest results are here: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=737104&view=results Unsure why the failure is occurring, but it may be due to this being a readme-only change. Once the other checks pass, an admin can merge this, however. |
…urce Manager Schema (Azure#12943) * Update readme files for csharp, az cli, and azureresourceschema * Fix spelling mistake * Fix bug from issue 744 * Add newline to end of readme files * First round of updates for Azure CLI code generation
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
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 Breaking Change 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.