Reactive plugin doesn't allow for other `charm` cli arguments.
Metadata
Current evaluation
Closed without resolution. The reactive plugin could not pass custom charm CLI arguments like --layer-index. Despite user requests for reproducible builds and binary wheel support, the feature was abandoned due to inactivity.
Suggested action: —
No scores available.
Issue body
The `charm-tools` builder `charm` allows for many build switches, some which are necessary to produce reproducible stable builds.
It doesn't seem that this plugin allows for any such options to be specified.
For instance, one cannot override the `layer-index` used during the build with this cli switch, so only the default is available.
```bash
-i LAYER_INDEX, --layer-index LAYER_INDEX
One or more index URLs used to look up layers,
separated by commas. Can include the token DEFAULT,
which will be replaced by the default index
(https://juju.github.io/layer-index/). E.g.:
https://my-site.com/index/,DEFAULT
```
https://github.com/canonical/charmcraft/blob/a2205cb1270220c03d244814468ea812e984c01c/charmcraft/reactive_plugin.py#L159-L165
it would be beneficial to reactive charms for `charmcraft` to build with these switches primarily as CLI switches or at a minimum `charmcraft.yaml` configuration options.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The reactive plugin could not pass custom charm CLI arguments like --layer-index. Despite user requests for reproducible builds and binary wheel support, the feature was abandoned due to inactivity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The feature request to pass additional charm CLI arguments to the reactive plugin was abandoned, with no fix merged or configuration added. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The reactive plugin limitation preventing custom charm CLI arguments like --layer-index remains unresolved. No fix or alternative solution was provided, indicating the request was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Reactive plugin support for custom charm CLI arguments was closed without implementation. The request was abandoned with no fix, merge, or configuration option added. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2194 Builds of charm using reactive plugin produces different config option | charmcraft | closed | Closed without resolution. Maintainers acknowledged the charmcraft 3 reactive plugin incorrectly strips deprecated config options, but no fix was implemented. | |
| #1816 Reactive charm built with charmcraft 3.x is missing options from the included layers and is broken | charmcraft | open | Reactive charms built with charmcraft 3.x lose config.yaml options from included layers; 2.x works. Maintainer acknowledged and plans a rewrite of the reactive build logic; reporter confirmed still broken on 3.4.3 and is willing to wait. | |
| #804 The reactive plugin is not correctly checking if `charm` failed | charmcraft | closed | Incorrect charm return code validation in the reactive plugin was abandoned and closed without a fix. No pull requests or follow-up actions were recorded. | |
| #924 reactive plugin: call `charm build` with `-v` | charmcraft | closed | Closed after triage and internal ticket creation. Implementation guidance was provided to pass verbose flags to charm calls when verbosity is trace or debug. No fix or pull request was merged. | |
| #863 reactive_plugin: Support arguments to charm build command | charmcraft | merged | Added reactive-charm-build-arguments to pass custom flags to the charm build command. Merged after approval and passing CI, resolving issue #809. | |
| #610 many: add reactive charm plugin | charmcraft | closed | Closed and superseded by pull request #613. The reactive charm plugin was replaced rather than merged. |