chore: Move OCI code into a helm module to hide implementation details.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading helm.rs and oci.rs in stackable-cockpit to understand how the current repository and OCI implementations are exposed to callers. Move the OCI-specific code behind the helm module so callers no longer depend on its implementation details, while preserving the currently supported installation methods.
Written by the indexing model from the issue text.
Description
We currently have helm.rs and oci.rs in stackable-cockpit. In the future we want to consolidate all repo-relevant code into a single module so that calling functions do not need to know about the underlying detail. This will become more relevant when:
- external dependencies no longer exclusively use repositories (as is currently the case for e.g. demos)
- other chart types such as
.tgzarchives are considered
N.B.
From the helm online help, installations can use:
- By chart reference: helm install mymaria example/mariadb
- By path to a packaged chart: helm install mynginx ./nginx-1.2.3.tgz
- By path to an unpacked chart directory: helm install mynginx ./nginx
- By absolute URL: helm install mynginx https://example.com/charts/nginx-1.2.3.tgz
- By chart reference and repo url: helm install --repo https://example.com/charts/ mynginx nginx
- By OCI registries: helm install mynginx --version 1.2.3 oci://example.com/charts/nginx
We currently implement 1, 5, 6.
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug core
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
JIT-compiled number -> Decimal conversion silently overflows instead of raising DECIMAL_OVERFLOW Openfuzz
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ClickHouse/ClickHouse#122114 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
linebender/vello_svg#90 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100