mayadata-io / mayadata-io/d-operators

experiment: verify deletion of a recipe does not delete lock of other recipe(s)

Open
#118 0 comments 0 reactions 0 assignees View on GitHub

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the Kubernetes controller and existing e2e coverage for recipe deletion, then run the relevant scenario; done means deleting one recipe leaves the locks belonging to every other recipe intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.