mayadata-io / mayadata-io/d-operators
feat: ability to debug a recipe
Open
Nobody has claimed this yet.
debug
recipe
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As an automation engineer I would like to know how a Recipe was execution. How many times it was skipped, had errors, executed, etc. In case of errors, what were the error messages.
NOTE: This is different from kind: RecipeGroupReport
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 entry points are named. Start by locating the Recipe execution and reporting paths, while keeping the behavior distinct from kind: RecipeGroupReport. Done should provide execution, skip, and error counts, along with error messages for failed executions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100