mayadata-io / mayadata-io/d-operators
experiment: verify state is not lost by recipe update action
Open
Nobody has claimed this yet.
e2e
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 has no body, file, test, or entry point to identify. Start by locating the recipe update action and related state or conformance tests in the d-operators repository; done would mean verifying that state remains intact after the action. Confirm that this old experiment is still relevant before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100