Handling multiple bundles in one repo
Metadata
Current evaluation
Closed without a code fix; maintainers advised placing each bundle in a separate subdirectory with its own charmcraft.yaml instead of supporting multiple bundle files in one directory.
Resolution: closed not a bug
Reason: Maintainer @sergiusens resolved the question in the closing comment on 2021-09-06 by recommending multiple subdirectories, each with its own charmcraft.yaml. No resolving PR or commit was recorded.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Right now we've got 3 bundles defined in https://github.com/canonical/bundle-kubeflow:
- `bundle.yaml`
- `bundle-lite.yaml`
- `bundle-edge.yaml`
It's useful to keep these all in the same repo. However, it seems that `charmcraft pack` is hardcoded to look for `bundle.yaml`. How should we handle multiple bundles defined in the same repo?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Closed without a code fix; maintainers advised placing each bundle in a separate subdirectory with its own charmcraft.yaml instead of supporting multiple bundle files in one directory. | |
| stealth/space-bunny-alpha | — | closed not a bug | No code change was made; maintainers directed users to place each bundle in a separate subdirectory with its own charmcraft.yaml. | |
| stealth/space-bunny-alpha | — | closed not a bug | Maintainers directed users to separate subdirectories, each with its own charmcraft.yaml; legacy bundle support was later removed by #2320. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed as working as designed: maintainers recommended separate subdirectories, each with its own charmcraft.yaml, instead of adding multi-bundle support. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed without a code fix: maintainers recommended separate subdirectories, each with its own charmcraft.yaml, for multiple bundles in one repository. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a code fix. Maintainers recommended using separate subdirectories with individual charmcraft.yaml files for each bundle as a workaround to support multiple bundles in a single repository. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned; no tool update provided. A maintainer recommended using separate subdirectories with individual charmcraft.yaml files to support multiple bundles in a single repository. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. Resolved via workaround: place each bundle in separate subdirectories with individual charmcraft.yaml files to bypass the hardcoded bundle.yaml lookup. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as answered. A maintainer recommended organizing multiple bundles into separate subdirectories, each with its own charmcraft.yaml file, rather than updating the pack command. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#373
(confidence 80%)
Adjacent discussion where maintainers described bundle.yaml as legacy and kept charmcraft.yaml dedicated to build definitions.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #373 Multiple files for packing a bundle is confusing | charmcraft | closed | Proposal to fold bundle.yaml into charmcraft.yaml was declined: sergiusens (2021-09-06) called bundle.yaml a legacy concept slated for replacement by stacks, keeping charmcraft.yaml build-only. Bundles were later deprecated (#2227) and removed in Charmcraft 4.0 (#2320). |