Skip to content
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

[AutoRelease] t2-confluent-2022-05-20-47659(Do not merge) #24532

Closed
wants to merge 10 commits into from

Conversation

azclibot
Copy link
Contributor

@azure-sdk
Copy link
Collaborator

@azclibot azclibot requested a review from msyyc as a code owner May 20, 2022 01:26
@ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label May 20, 2022
@ghost
Copy link

ghost commented May 20, 2022

Thank you for your contribution azclibot! We will review the pull request and get back to you soon.

@check-enforcer
Copy link

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this pull request Jun 27, 2023
[Hub Generated] Review request for Microsoft.MachineLearningServices to add version preview/2023-06-01-preview (Azure#24049)

* Adds base for updating Microsoft.MachineLearningServices from version preview/2023-04-01-preview to version 2023-06-01-preview

* Updates readme

* Updates API version in new specs and examples

* MFE 2023-06-01-preview staging (Azure#24051)

* Updated mfe.json

* Added package example

* Updated custom-words.txt

* Updated package examples

* Added pattern retriction to resource name parameters

* Fixed cross-api breaking changes

* Fixed cross-api breaking changes

* Added descriptions

* Added description

* Separate workspace rp swagger from mlc (Azure#24249)

* separate workspace rp swagger from mlc

* add missing parameter

* Updated mfe.json descriptions for put 200 responses (Azure#24295)

* update EnableNodePublicIp for computeInstance of MLC (Azure#24231)

Co-authored-by: Bingchen Li <bingchenli@microsoft.com>

* Update workspaceRP swagger with automation result (Azure#24333)

* Update workspace rp swagger with automation result

rename pe definition to avoid conflict

fix

update PE name

Update connection credential

hide armid

fix more things

Fix enum issue

fix polymorphism

Update examples

Update body name and example

fix more issue

update response body

Fix

Revert "file change"

This reverts commit 4a1fdccf6eb22e1dda82d3acce8065fae171f422.

file change

Update swagger

fix errors

update format

add example for connetion list secrets api

run prettier

* Fixing more issue

* revert custom-words

* run prettier

* Update securityDefinitions

* Revert operation id

* Update description and summary.

* fix prettier issue and add description

* remove redundent object definition

* fixing swagger issue

revert PaginationParameter

* Revert back to old file with only reorder for better compare

* Revert "Revert back to old file with only reorder for better compare"

This reverts commit 8feb7d84319124ff3a447daffef894da18ef0077.

* Revert connection v2 tag issue

* Add back delete op for network rule

* Add back example for the removed API

* Suppress header check caused by old design

* fix delete rule in path

* Update example error

* Update delete rule api and remove suppression

* Fixed merge conflicts in custom-words.txt (Azure#24532)

---------

Co-authored-by: ZhidaLiu <zhili@microsoft.com>
Co-authored-by: libc16 <88697960+libc16@users.noreply.github.com>
Co-authored-by: Bingchen Li <bingchenli@microsoft.com>
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants