stackabletech / stackabletech/stackablectl
Make installation of stack steps conditional
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 4
Description
Description
Some demos have requirements that can only be installed at stack installation time. Examples are: airflow dags, jupyter notebooks. These cannot be installed by the demo it's self because that's too late.
Currently some stacks install resources that only make sense as part of demos. This can be confusing and leads to stack pollution with unnecessary steps and resources.
Proposed solution
Introduce some mechanism that allows stacks to create resources conditionally.
In the examples above, stacks should install airflow dags and jupyter notebooks conditionally. The corresponding demos would enable the condition while the stacks would not.
Alternatively, demo stacks could be separated from the "official" stacks.
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 how stack installation and demo selection are handled in stackablectl, especially the paths that install Airflow DAGs and Jupyter notebooks. Define a mechanism for demos to enable conditional resources while official stacks omit them, or determine how separate demo stacks would work; done means unnecessary demo resources are no longer installed by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, rust
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100