-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Deprecate feature flag for Custom threshold rule #172584
Deprecate feature flag for Custom threshold rule #172584
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ResponseOps changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just added one question :)
@benakansara I see these instances in the code: (from what I see you only removed one of them) |
For the first line, same reason as #172554 (comment) I didn't remove instances from serverless tests, as I wasn't sure about how to deprecate/remove existing feature flag from there. |
@maryam-saeidi I have removed feature flag usages from serverless tests. |
/oblt-deploy-serverless |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @benakansara |
Resolves elastic#171406 - Deprecates following feature flag used for enabling/disabling Custom threshold rule: ``` xpack.observability.unsafe.thresholdRule.enabled ``` - Removes usage of this flag from code. - Adding this flag in `kibana.yml` will generate following warning: ``` [WARN ][config.deprecation] You no longer need to configure "xpack.observability.unsafe.thresholdRule.enabled". ``` --------- Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 16f09fd)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…72792) # Backport This will backport the following commits from `main` to `8.12`: - [Deprecate feature flag for Custom threshold rule (#172584)](#172584) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bena Kansara","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-12-07T09:34:11Z","message":"Deprecate feature flag for Custom threshold rule (#172584)\n\nResolves https://github.com/elastic/kibana/issues/171406\r\n\r\n- Deprecates following feature flag used for enabling/disabling Custom\r\nthreshold rule:\r\n```\r\nxpack.observability.unsafe.thresholdRule.enabled\r\n```\r\n- Removes usage of this flag from code.\r\n- Adding this flag in `kibana.yml` will generate following warning:\r\n```\r\n[WARN ][config.deprecation] You no longer need to configure \"xpack.observability.unsafe.thresholdRule.enabled\".\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <[email protected]>","sha":"16f09fdcc45a2df9a3a7868ea9590227627b82ad","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.12.0","Team:obs-ux-management","v8.13.0"],"number":172584,"url":"https://github.com/elastic/kibana/pull/172584","mergeCommit":{"message":"Deprecate feature flag for Custom threshold rule (#172584)\n\nResolves https://github.com/elastic/kibana/issues/171406\r\n\r\n- Deprecates following feature flag used for enabling/disabling Custom\r\nthreshold rule:\r\n```\r\nxpack.observability.unsafe.thresholdRule.enabled\r\n```\r\n- Removes usage of this flag from code.\r\n- Adding this flag in `kibana.yml` will generate following warning:\r\n```\r\n[WARN ][config.deprecation] You no longer need to configure \"xpack.observability.unsafe.thresholdRule.enabled\".\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <[email protected]>","sha":"16f09fdcc45a2df9a3a7868ea9590227627b82ad"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172584","number":172584,"mergeCommit":{"message":"Deprecate feature flag for Custom threshold rule (#172584)\n\nResolves https://github.com/elastic/kibana/issues/171406\r\n\r\n- Deprecates following feature flag used for enabling/disabling Custom\r\nthreshold rule:\r\n```\r\nxpack.observability.unsafe.thresholdRule.enabled\r\n```\r\n- Removes usage of this flag from code.\r\n- Adding this flag in `kibana.yml` will generate following warning:\r\n```\r\n[WARN ][config.deprecation] You no longer need to configure \"xpack.observability.unsafe.thresholdRule.enabled\".\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <[email protected]>","sha":"16f09fdcc45a2df9a3a7868ea9590227627b82ad"}}]}] BACKPORT--> Co-authored-by: Bena Kansara <[email protected]>
Resolves #171406
kibana.yml
will generate following warning: