vexxhost / vexxhost/migratekit
Destination project
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 138
- Forks
- 40
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Currently when I run migratekit it creates the volumes and instance in the same project as the migratekit vm is running. Is there a way to specify a destination project for where these items are to be created?
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing migratekit's current volume and instance creation paths and how they select the project from the VM environment. Define how a destination project would be supplied and verify that both created resources use it; the issue provides no file or test names, so repository-wide searching is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100