Way to migrate application across PipeCD projects
Open
Nobody has claimed this yet.
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:
Why is this needed:
In some use cases, users want to move/migrate one application from a PipeCD project to another project without downtime. Currently, it's hard to make it due to the PipeCD resource control mechanism (based on the resource annotations).
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 names no files, tests, or entry points. Start by tracing PipeCD's resource control mechanism and how applications are associated with projects; define the migration flow and its no-downtime requirements before identifying the affected components and tests. Done means an application can move between projects without downtime or resource-control conflicts.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100