`v1beta1` API "epic"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
This issue will be used as an Epic to track work, discussion and design doc towards a v1beta1 API for the operator.
Some open questions:
- Keep only
TektonConfigand removeTektonPipeline - How to manage "end-user" data (secrets for chains, …)
- Profiles versus list of components to install
- Design for "extensibility" : aka how does it interact with a *possible" upstream OpenShift Pipelines operator that depends / encapsulate
tektoncd/operator.
cc @tektoncd/operator-maintainers @tektoncd/operator-collaborators
I think the next action item for this is going to be create a hackmd or google doc exploring some potential design
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 four open design questions and the proposed HackMD or Google Doc, then map the discussion into a v1beta1 API design for the operator. Done means the scope and design decisions are documented, including TektonConfig/TektonPipeline, end-user data, profiles, components, and extensibility.
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
- 20/100