-
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
[ResponseOps] Remove 7.x deprecated kibana.yml settings #198435
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
…alerts.healthCheck
💚 Build Succeeded
Metrics [docs]
History
|
Pinging @elastic/response-ops (Team:ResponseOps) |
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.
Mind adding release_note:breaking
?
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 👍
Seeing the
Do we need some things removed from there as well? |
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, except the comment I left about queueing empheral tasks. Guessing there will be more work to remove all the ephermal task stuff, but seems like we should stop queueing them in this PR. Pinged Mike because I don't know the full context here.
@@ -183,11 +180,7 @@ export class ActionScheduler< | |||
enqueueOptions: EnqueueExecutionOptions; | |||
bulkScheduleRequest: EnqueueExecutionOptions[]; | |||
}) { | |||
if ( |
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.
This doesn't seem quite right. If for some reason this.context.taskRunnerContext.supportsEphemeralTasks
becomes true, I think we'd end up scheduling all the tasks with it, whereas before we would have only done context.taskRunnerContext.maxEphemeralActionsPerRule
of them.
I wonder if we should either remove queueing these as emphermeral completely here, or something else. @mikecote ?
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.
okay sounds good, thanks!
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.
Resolved in this commit 375e71e
Yes, thanks! Here is the cloud pr https://github.com/elastic/cloud/pull/133738 |
Resolves #194622
Summary
Removes the following deprecated configuration settings:
xpack.actions.customHostSettings.ssl.rejectUnauthorized
xpack.actions.whitelistedHosts
xpack.actions.rejectUnauthorized
xpack.actions.proxyRejectUnauthorizedCertificates
xpack.alerts.healthCheck
xpack.alerts.invalidateApiKeysTask.interval
xpack.alerts.invalidateApiKeysTask.removalDelay
xpack.alerting.defaultRuleTaskTimeout