mayadata-io / mayadata-io/d-operators
use case: custom controller to simplify api testing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As an automation engineer I want to verify my use case by testing its REST APIs. Most of the times, a feature consists of one or more invocations to REST APIs. Some of these APIs need to parse output from previous API invocations. All of these APIs need some kind of authentication to succeed.
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 reviewing the existing controller and API-testing patterns in the repository, then clarify how chained REST calls, output passing, and authentication should be configured. Done would require an agreed design and tests covering the custom controller's supported use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend-api-design, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100