mayadata-io / mayadata-io/d-operators
experiment: verify deletion of a recipe does not delete some other configmap(s)
Open
Nobody has claimed this yet.
build
e2e
experiment
good first issue
recipe
testing
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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
The issue names no files or tests. Start by locating the repository's end-to-end controller tests and the recipe deletion path, then reproduce deletion with multiple ConfigMaps. Done means deleting one recipe leaves unrelated ConfigMaps unchanged and the verification is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100