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

conditionally enable searching for alert groups via env var #4287

Merged
merged 12 commits into from
Jun 4, 2024

Conversation

sreway
Copy link
Contributor

@sreway sreway commented Apr 26, 2024

What this PR does

re-enables the search for alert groups

Which issue(s) this PR closes

Closes #2232

Checklist

  • Unit, integration, and e2e (if applicable) tests updated
  • Documentation added (or pr:no public docs PR label added if not required)
  • Added the relevant release notes label (see labels prefixed w/ release:). These labels dictate how your PR will
    show up in the autogenerated release notes.

@sreway sreway requested review from a team April 26, 2024 11:46
@fantom0005
Copy link

Could you please add this solution to Incident's Public API?
I mean there https://github.com/grafana/oncall/blob/dev/engine/apps/public_api/views/incidents.py#L37.

If it is possible

Copy link
Contributor

@joeyorlando joeyorlando left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 thank you for your contribution @sreway!

grafana-plugin/src/models/alertgroup/alertgroup.ts Outdated Show resolved Hide resolved
@joeyorlando joeyorlando changed the title enable searching for alert groups conditionally enable searching for alert groups Apr 26, 2024
@joeyorlando joeyorlando changed the title conditionally enable searching for alert groups conditionally enable searching for alert groups via env var Apr 26, 2024
@joeyorlando joeyorlando added pr:no public docs Added to a PR that does not require public documentation updates release:patch PR will be added to "Other Changes" section of release notes labels Apr 26, 2024
@joeyorlando
Copy link
Contributor

@sreway if you don't mind address the linting CI errors I can go ahead and merge this! (run pre-commit run --all-files locally)

sreway and others added 2 commits April 27, 2024 13:02
@sreway
Copy link
Contributor Author

sreway commented Apr 27, 2024

Could you please add this solution to Incident's Public API? I mean there https://github.com/grafana/oncall/blob/dev/engine/apps/public_api/views/incidents.py#L37.

If it is possible

This solution will not work with the public API. You can create a feature request to extend the filtering of alert groups.

@joeyorlando joeyorlando requested a review from maskin25 May 13, 2024 17:14
@joeyorlando
Copy link
Contributor

@maskin25 are things okay from your point of view?

@sreway sreway temporarily deployed to github-pages June 4, 2024 11:43 — with GitHub Actions Inactive
@joeyorlando joeyorlando removed the request for review from maskin25 June 4, 2024 11:44
@joeyorlando joeyorlando enabled auto-merge June 4, 2024 11:44
@joeyorlando joeyorlando added this pull request to the merge queue Jun 4, 2024
Merged via the queue into grafana:dev with commit 0acb66b Jun 4, 2024
18 checks passed
@vadimkerr vadimkerr mentioned this pull request Jun 4, 2024
3 tasks
github-merge-queue bot pushed a commit that referenced this pull request Jun 4, 2024
# What this PR does

Only validate live settings in `AVAILABLE_NAMES` to avoid issues when a
live setting is renamed (one of the settings was renamed in
#4287 earlier)

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] Added the relevant release notes label (see labels prefixed w/
`release:`). These labels dictate how your PR will
    show up in the autogenerated release notes.
brojd pushed a commit that referenced this pull request Sep 18, 2024
# What this PR does

re-enables the search for alert groups

## Which issue(s) this PR closes

Closes #2232

<!--
*Note*: if you have more than one GitHub issue that this PR closes, be
sure to preface
each issue link with a [closing
keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue).
This ensures that the issue(s) are auto-closed once the PR has been
merged.
-->

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] Added the relevant release notes label (see labels prefixed w/
`release:`). These labels dictate how your PR will
    show up in the autogenerated release notes.

---------

Co-authored-by: Joey Orlando <[email protected]>
Co-authored-by: Joey Orlando <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:no public docs Added to a PR that does not require public documentation updates release:patch PR will be added to "Other Changes" section of release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

re-enable free-text searching on alert groups
5 participants