You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[FR] Include Timeline Templates export/import in the CLI such that they can be imported and exported together with rules like exceptions and action connectors
#4588
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.
Currently, timeline templates are referenced by id and name in the exported rule files. However, the tempalte itself is not exported/cannot be imported via the CLI.
Best would be to implement this analog to the exception lists and action connectors. I hope its possible to use the same concepts and just adapt the code to the Timeline Template API.
Considered Alternatives
No response
Additional Context
This feature is essential for our DaC workflows for customer projects, so we are thinking about taking a look at the code base and checking if we can contribute to this, in case there are currently no plans of implementing this by elastic.
Thus, I wanted to ask if there are already some plans for this or if there has already been progress in the background or anything 🙂
The text was updated successfully, but these errors were encountered:
Repository Feature
None
Problem Description
Currently, timeline templates are referenced by id and name in the exported rule files. However, the tempalte itself is not exported/cannot be imported via the CLI.
This limitations is also mentioned in the DaC Documentation.
Desired Solution
The Kibana API exists.
Best would be to implement this analog to the exception lists and action connectors. I hope its possible to use the same concepts and just adapt the code to the Timeline Template API.
Considered Alternatives
No response
Additional Context
This feature is essential for our DaC workflows for customer projects, so we are thinking about taking a look at the code base and checking if we can contribute to this, in case there are currently no plans of implementing this by elastic.
Thus, I wanted to ask if there are already some plans for this or if there has already been progress in the background or anything 🙂
The text was updated successfully, but these errors were encountered: