project-codeflare / project-codeflare/codeflare-sdk
Potential cluster.up() behavior update
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 66
- Avg merge
- 48m
- Merged PRs (30d)
- 7
Description
Currently, cluster.up() throws an exception when a cluster with the same name (in the same namespace) already exists. Investigate changing this behavior, and see if any issues would arise from allowing it to overwrite the existing cluster (and if so, maybe still make it an option)
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
Start at the cluster.up() entry point and trace how it handles an existing cluster with the same name in the same namespace. Investigate the effects of overwriting that cluster and whether replacement should be optional. Done means documenting the chosen behavior and its implications clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100