Create way for task-runner to store DMS metadata about a task
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Something like this might be necessary for task-runner to store/retrieve metadata about the
underlying "task" being executed in DMS.
This might not be necessary if we are able to use only the studio IDs for things, like receiving a callback
with the task ID and updating only the storage.
As we build more complex pipelines tho, like for example `task-runner` doing any finalization logic after
the DMS part is done, we might need something like this not to depend only on RabbitMQ for persistence.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or code entry points are named. Start by tracing the task-runner flow and its RabbitMQ interaction, then clarify whether DMS metadata storage is required or studio IDs and storage are sufficient; completion criteria are not defined in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rabbitmq, typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100