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-mobilenetwork-2022-02-20-80861(Do not merge) #23151

Merged
merged 3 commits into from
Feb 28, 2022

Conversation

azclibot
Copy link
Contributor

@azure-sdk
Copy link
Collaborator

@ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Feb 20, 2022
@ghost
Copy link

ghost commented Feb 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

@msyyc
Copy link
Member

msyyc commented Feb 28, 2022

/azp run prepare-pipelines

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@msyyc msyyc merged commit 0549c06 into Azure:main Feb 28, 2022
@msyyc msyyc deleted the t2-mobilenetwork-2022-02-20-80861 branch February 28, 2022 04:36
rakshith91 pushed a commit to rakshith91/azure-sdk-for-python that referenced this pull request Apr 10, 2022
…23151)

* code and test

* Update CHANGELOG.md

Co-authored-by: PythonSdkPipelines <PythonSdkPipelines>
Co-authored-by: Yuchao Yan <[email protected]>
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this pull request Apr 14, 2023
Release sentinel 2023 04 01 preview (Azure#23121)

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

* Updates readme

* Updates API version in new specs and examples

* Workspace Manager Members (Azure#23134)

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

* Updates readme

* Updates API version in new specs and examples

* Workspace Manager Members

* udpate pattern

* Workspace manager configurations (Azure#23133)

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

* Updates readme

* Updates API version in new specs and examples

* adding april configurations swagger

* update pattern

* prettier update

* update readme

* Workspace manager assignments (Azure#23130)

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

* Updates readme

* Updates API version in new specs and examples

* Workspace Manager Assignments/Jobs

* update readme

* updated from comments

* update from lint diff errors

* updated descriptions

* Workspace manager groups (Azure#23135)

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

* Updates readme

* Updates API version in new specs and examples

* april swagger for groups

* update path name & pattern

* [Hunts] Add hunts to Sentinel 2023-04-01-preview version (Azure#23139)

* Add hunts files

* Include update in 200 description and add defaults

* Add back 201

* Update relation properties

* Update example

---------

Co-authored-by: Derrick Lee <[email protected]>

* Add readonly flag to providerName property (Azure#23259)

* sentinel content hub package and template API (Azure#23151)

* commit for content template and content package API

* fix issues reported by swagger lint

* add 201 for put requests in template service

* resolve the comments

* resolve comments in packageId

* resolve comments

* update descriptions due to lint error (Azure#23392)

* Fix policheck issue by updating the description. (#23415)

* Fix polich issue by updating the description.

* update the description to fix a typo.

* Release sentinel 2023 04 01 preview (Azure#23420)

* Fix polich issue by updating the description.

* update the description to fix a typo.

* fix policheck by updating description

* rename enum name to stable version to fix cross-version breaking change failure.

* fix typo (Azure#23463)

---------

Co-authored-by: rheabansal <[email protected]>
Co-authored-by: Derrick Lee <[email protected]>
Co-authored-by: Derrick Lee <[email protected]>
Co-authored-by: Anat Gilenson <[email protected]>
Co-authored-by: xuhumsft <[email protected]>
Co-authored-by: Nan Zang <[email protected]>
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.

3 participants