mayadata-io / mayadata-io/d-operators
design: recipe should differentiate between action, action on collection & bulk action
Open
Nobody has claimed this yet.
action
bulk
design
recipe
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
kind: Recipe
spec:
tasks:
- assert:
- assertAll:
- bulkAssert:
- delete:
- deleteAll:
- bulkDelete:
Where:
- action implies an action against a single resource instance
- actionAll implies actions against one or more resource instances of same apiversion, kind & namespace
- bulkAction implies actions against one or more resources belonging to one or more apiversion, kind & namespace combinations
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
Use the YAML Recipe example and the three action definitions in the issue as the starting point. The work is complete when the Recipe representation clearly distinguishes single-resource actions, same-scope collection actions, and bulk actions across apiversion, kind, and namespace combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100