Skip to content

Feature/query sdk#19006

Merged
rakshith91 merged 3 commits intoAzure:feature/query-sdkfrom
rakshith91:feature/query-sdk
May 30, 2021
Merged

Feature/query sdk#19006
rakshith91 merged 3 commits intoAzure:feature/query-sdkfrom
rakshith91:feature/query-sdk

Conversation

@rakshith91
Copy link
Contributor

No description provided.

@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

@rakshith91 rakshith91 force-pushed the feature/query-sdk branch from 7ca7851 to 05f1c79 Compare May 30, 2021 07:15
@rakshith91 rakshith91 merged commit cfbd5e4 into Azure:feature/query-sdk May 30, 2021
rakshith91 pushed a commit that referenced this pull request Jun 5, 2021
* Azure monitor query (#18022)

* Initial commit

* updates

* packaging

* namespace

* oops

* regenerate

* shared reqs

* sample test file

* AAD support

* samples

* ci fix

* lint

* docs

* models

* more changes

* update

* minor update

* batcg support

* minor update

* logs

* mypy

* more changes

* definition

* changes

* sampes

* lint

* Feature/query sdk (#18993)

* lint

* update samples

* Feature/query sdk (#19006)

* query

* add async

* readme

* Feature/query sdk (#19007)

* query

* add async

* aio

* query (#19056)

add async

metrics

models

models refactor

samples fix

* temporary readme links (#19057)

* lint (#19058)

* oops (#19059)

* lint 2 (#19061)

* Lint 3 (#19073)

* lint 2

* lint-3

* Add tests (#19076)

* Apply suggestions from code review

* analyze + stubgen (#19082)

* snake case refactor (#19084)

* aio tests (#19092)

* Timespan (#19100)

* fix definitions

* fix name space

* aio namespace

* order results

* tests fix

* py2 compat

* azure monitor nspkg (#19101)

* Lint + feedback (#19108)

* Revert "azure monitor nspkg (#19101)"

This reverts commit c919183.

* lint + feedback

* timespan (#19110)

* Update sdk/monitor/azure-monitor-query/azure/monitor/query/_log_query_client.py

* lint + async (#19114)

* Lint (#19120)

* lint + duration

* changelog

* Apply suggestions from code review

* Apply suggestions from code review

* Update sdk/monitor/azure-monitor-query/tests/conftest.py

* Update sdk/monitor/azure-monitor-query/setup.py

* freeze req (#19124)

* Update sdk/monitor/azure-monitor-query/samples/async_samples/sample_metric_definitions_async.py
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.

1 participant