PipeCD plugin architecture
Open
@khanhtc1202 is already working on this.
Since Jan 30, 2025.
area/pipedv1
epic
kind/enhancement
not-auto-close
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What would you like to be added:
This issue is the meta (epic) issue that links all issues related to adopting plugin architecture for PipeCD.
- Piped plugin architecture (v1.0 for piped) supports applications' deployments ref: #4980
- Make control plane support both piped v0 and v1 (plugin-arched piped) ref: #5252
- Livestate feature in plugin architecture ref: #5363
- Support stages as plugins https://github.com/pipe-cd/pipecd/issues/5367
- Migrate from pipedv0 -> pipedv1 https://github.com/pipe-cd/pipecd/issues/5542
Related issues:
- Remove deprecated features/codebase from pipedv1 https://github.com/pipe-cd/pipecd/issues/5956
Why is this needed:
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.
Assessment
This issue has not been assessed yet.