influxdata / influxdata/kapacitor
Allow recordings to be defined via the API
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Recordings are a useful tool for validating the Kapacitor + TICKscripts are working as expected. Currently there is no way to create a recording besides creating a task an performing a recording. It would be nice if they could be created directly via the API instead of indirectly through a task. This would allow for external data sources i.e. version control or the like to be used as the source of the data.
Contributor guide
Research direction
Start by tracing how recordings are currently created through tasks and where the existing API exposes recording-related operations. Define the direct API input and completion criteria around creating recordings without a task, including support for external data sources such as version control.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100