Include/Exclude filters do not split comma-separated values
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start at the stackablectl release install command and trace how the --include and --exclude options are parsed. Reproduce the issue with stackablectl release install 25.3 -e airflow,druid; done means comma-separated values exclude both operators, or the command reports an invalid value clearly.
Written by the indexing model from the issue text.
Description
@xeniape found this bug
Affected version
25.3.0
Current and expected behavior
Current Behaviour:
stackablectl release install 25.3 -e airflow,druid
This installs all operators. None are excluded, because there is no operator named airflow,druid.
Expected behaviour:
The help text suggest you can specify multiple values (INCLUDED_PRODUCTS and EXCLUDED_PRODUCTS):
Options:
-i, --include <INCLUDED_PRODUCTS>
Whitelist of product operators to install
-e, --exclude <EXCLUDED_PRODUCTS>
Blacklist of product operators to install
stackablectl release install 25.3 -e airflow,druid
This should install all operators for the release, except airflow and druid.
Possible solution
Try to unmarshall the comma-separated list of operators (or at least error out).
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
maybe
- 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
-
todo:perf
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
ACP agents get no MCP servers when the thread is created before the project's first worktree loads Openstate:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zed-industries/zed#64611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
objectionary/phie#154 ·