[ResponseOps][Reporting] Re generate api key when updating scheduled reports run schedule#253767
Merged
adcoelho merged 1 commit intoelastic:mainfrom Feb 19, 2026
Merged
Conversation
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
cc @adcoelho |
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Feb 19, 2026
…reports run schedule (elastic#253767) Closes elastic#245086 ## Summary As a follow-up to the changes in elastic#249109 I am updating the call to bulkUpdateSchedules to regenerate the API key. I used elastic#244918 as a reference where the description says: > If a task with an API key is updated with a request, we **should** invalidate the old API key and create a new API key using the new request. ## Testing 1. Create a scheduled report which should run soon 2. Verify that created scheduled report ran successfully in the Reporting > Exports tab 3. Update the report to run soon again via Reporting > Schedules or via API 4. Confirm that the edited scheduled report ran successfully
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #245086
Summary
As a follow-up to the changes in #249109 I am updating the call to bulkUpdateSchedules to regenerate the API key.
I used #244918 as a reference where the description says:
Testing