Handling multiple bundles in one repo
Metadata
Current evaluation
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a code fix. Resolution recommends organizing each bundle into separate subdirectories with individual charmcraft.yaml files to enable multi-bundle repository support. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #373 Multiple files for packing a bundle is confusing | charmcraft | closed | Request to merge bundle.yaml into charmcraft.yaml was rejected. bundle.yaml is legacy and being replaced by stacks. charmcraft.yaml remains strictly for build-time definitions. Users should construct bundles using the parts syntax with the bundle plugin instead. |