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

[8.x] [Response Ops][Task Manager] Changing task manager `schedule.interval` schema to string from duration (#204413) #204669

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…` schema to string from duration (elastic#204413)

## Summary

Currently, when task manager schema changes are migrated down (which can
occur during a release when there are multiple Kibana nodes running and
they get updated one after another), we are running into this bug:
elastic#204395 where the task
`schedule.interval` gets mutated from expected values (like `60s`) to
unallowed (but still valid for the schema) values (like `PT1M`).

This changes the schema for `schedule.interval` to use a string with
validation function.

## To verify
1. Run Kibana on `main` and create some rules that run frequently.
2. "Upgrade" to this PR branch and verify that rules continue to run.
3. "Downgrade" back to `main` and verify that rules continue to run.

(cherry picked from commit ccdd662)
@kibanamachine kibanamachine merged commit af953f4 into elastic:8.x Dec 18, 2024
11 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @ymao1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants