Check if the requested demo/stack exists before deploying kind cluster
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes, rust
- Domain
- cli, infrastructure
Research direction
Start from the stackablectl stack install command and trace the validation path before kind cluster creation. Reproduce with the invalid demo name shown in the issue; done means invalid stack or demo parameters are rejected before a kind cluster is created.
Written by the indexing model from the issue text.
Description
When running stackablectl it does not check to see if the stack or demo exists prior to creating a kind cluster. It should test the parameters are valid before deploying a cluster to avoid confusion and delay.
╰─ stackablectl stack install thisDoesNotExist --kind-cluster
[INFO ] Creating kind cluster stackable-data-platform
Creating cluster "stackable-data-platform" ...
✓ Ensuring node image (kindest/node:v1.24.0) 🖼
⢎⡱ Preparing nodes 📦 📦 📦 📦
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 4
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.
More from stackabletech/stackablectl
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/stackablectl#456 ·
-
RUSTSEC-2026-0221: `event-listener` allows `!Send` tags to cross thread boundaries via `StackSlot` Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
stackabletech/stackablectl#452 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
stackabletech/stackablectl#444 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
stackabletech/stackablectl#419 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/stackablectl#413 ·
All issues in stackabletech/stackablectl
Similar issues
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
longbridge/gpui-kit#3223 ·
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rocky-data/rocky#2181 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
[indexer] [QA] Add a focused test for the new NonRetryableError / assertSocketAlive() behavior. Openbot:ai-assisted component:indexer QA-roadmap status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
midnightntwrk/midnight-indexer#1557 ·