-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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][Alerting] Ability to bulk update API keys for alerting rules #139036
[ResponseOps][Alerting] Ability to bulk update API keys for alerting rules #139036
Conversation
…kibana into alerting/bulk-update-api-keys
Pinging @elastic/response-ops (Team:ResponseOps) |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
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! Works as expected.
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, works as expected. Check the API key of a rule updated with this gesture, and it changed when complete.
@mikecote - I'm curious what our ongoing story with "bulk" editing is. We have a bunch of other "bulk" editing capabilities in Not a blocker for this PR, if we wanted to enable an actual "bulk" update API key API, could be done in a subsequent PR. |
@pmuellr Yeah, separate API would make sense from my perspective. We don't call the update API to update the API key, same could be said about the bulk. We should for sure create a follow-up issue for backlog purposes. |
Created issue move "bulk update API keys" into the "bulk" route #139313 to track that, thx |
…rules (elastic#139036) * Adding bulk update api keys * Adding tests
Resolves #138011
Summary
Allows users to bulk update API keys for alerting rules in the rules table.
Checklist
To verify
Manage rules
button