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

add doc on how to create api view in rlc quickstart #19907

Merged
merged 3 commits into from Apr 18, 2022

Conversation

dw511214992
Copy link
Member

No description provided.

@dw511214992
Copy link
Member Author

/check-enforcer override

@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 js - [service] - ci

@dw511214992
Copy link
Member Author

/check-enforcer override

@dw511214992 dw511214992 merged commit 286e2f9 into main Apr 18, 2022
@dw511214992 dw511214992 deleted the dw/add-api-view-to-rlc-quickstart branch April 18, 2022 02:42
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-js that referenced this pull request Aug 5, 2022
[Hub Generated] Review request for Microsoft.MachineLearningServices to add version preview/2022-06-01-preview (Azure#19842)

* Adds base for updating Microsoft.MachineLearningServices from version stable/2022-05-01 to version 2022-06-01-preview

* Updates readme

* Updates API version in new specs and examples

* Add idleShutdownSetting to Compute Instances (Azure#19748)

* Added idleTimeBeforeShutdown to compute instance properties

* Added api UpdateIdleShutdownSetting

Co-authored-by: Teo Magnino Chaban <teom@microsoft.com>

* Add mfe.json 2022-06-01-preview changes (Azure#19740)

* update mfe.json with 2022-06-01-preview spec

* update go.md with preview-2022-06

* add AutoMLJob examples (initial)

* add LabelingJob examples (initial)

* add Schedule examples (initial)

* prettier

* update AutoMLJob examples

* update LabelingJob examples

* update LabelingJob examples

* prettier

* typo fixes

* add Vectorizer to custom-words.txt

* add missing

* is this a breaking change?

* Revert "update go.md with preview-2022-06"

This reverts commit b49c64ae0eb258069251c8c13085fd1e5dde56e2.

* Updating Swagger Spec for MLC for CustomServices (Azure#19781)

* Updating Swagger Spec for MLC for CustomServices

* Added Examples

* Removing update API in favor of exisiting Patch API and Fixing some Validation issues

* Fixed Pretty Issue

* Fixed Id Issue

* Changed case

* Updated Examples

* Changing Description

* Added nullable fields

* Added update APIs

* Fixing validation errors

* Fix model validation

Co-authored-by: Srivatsa Sinha <srsinha@microsoft.com>

* Add encryption property to workspace update parameters (Azure#19893)

* Add encryption property to workspace update parameters

Adding the ability for users to update CMK keyIdentifier property for workspace update.

* Apply prettier changes

Co-authored-by: Joshua Loeffler <jloeffler@microsoft.com>

* Add enum value to OutputDataDeliveryMode (Azure#19964)

* add soft delete related properties (Azure#19907)

* add soft delete related properties

* resolve lint diff issue that enum name duplicaton

Co-authored-by: Xi Jin <jinxi@microsoft.com>

* Remove SoftDeleteEnabled. (Azure#20005)

* reorder DeploymentResourceConfiguration Definition (Azure#20057)

Co-authored-by: Teddy Todorov <forteddyt@gmail.com>
Co-authored-by: teochaban <teochaban@hotmail.com>
Co-authored-by: Teo Magnino Chaban <teom@microsoft.com>
Co-authored-by: Teddy Todorov <thtodoro@microsoft.com>
Co-authored-by: srivatsasinha <102133347+srivatsasinha@users.noreply.github.com>
Co-authored-by: Srivatsa Sinha <srsinha@microsoft.com>
Co-authored-by: jloeffler7 <102193043+jloeffler7@users.noreply.github.com>
Co-authored-by: Joshua Loeffler <jloeffler@microsoft.com>
Co-authored-by: XI JIN <giovannijin1990@gmail.com>
Co-authored-by: Xi Jin <jinxi@microsoft.com>
Co-authored-by: ZhidaLiu <86350902+ZhidaLiu@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants