We need to support config files
Metadata
Current evaluation
The layered CLI configuration proposal was closed without an identified implementation; multiple-file stacking was explicitly deferred on 2020-06-03.
Resolution: closed stale
Reason: Maintainer @chipaca deferred multiple-file support to a later iteration, but no resolving PR, commit, or closing reference was found. The proposal was therefore abandoned without completing its stated layered CLI configuration scope.
Evaluated by: mr-cal-bot
No scores available.
Issue body
**Multilayer**: we will merge multiple configuration files, in this order (the latter prevails):
- system: `/etc/charmcraft.yaml`
- user: `($XDG_CONFIG_DIR)/charmcraft.yaml`
- local dir: `charmcraft.yaml` and `.charmcraft.yaml`
- command-line received options
**Discoverable**: the same parameters used in command line (shown with `--help` from the tool) can be applied in the config files. In this POV, the config file is just "a way to avoid needing to pass the same option through the command line"
**Format and structure**: We'll use a YAML file. Internally, it will be separated by commands (as different commands may have equally named option names). General options can be used in the generic `charmcraft` section, but also overriden in the commands. A example valid YAML:
```
charmcraft:
verbose: true
build:
requirements:
- reqs-legacy.txt
- reqs-new.txt
deploy:
verbose: 0
```
**Explicitness**: We'll log in debug which files were found and processed, and the final loaded configuration (after merging all those files and given command line modifiers).
**Some details about options types:**
- if the command line option is a flag (like `verbose`, not expecting a value, as you just saying you want verbose by using the flag), in the YAML it's converted to a bool (valid values are 0/1, false/true, no/yes).
- if the command line option is "multiple" (can be given multiple times), in the YAML file we will support either it being a value, or a list of values
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | The layered CLI configuration proposal was closed without an identified implementation; multiple-file stacking was explicitly deferred on 2020-06-03. | |
| stealth/space-bunny-alpha | — | closed stale | The layered system/user/local configuration proposal was narrowed to one local file, then closed without a linked implementation; no resolving PR or commit was found. | |
| stealth/space-bunny-alpha | — | closed stale | The multi-layer CLI configuration proposal was abandoned; layered-file support was deferred, and no resolving PR or commit was linked when #5 closed. | |
| stealth/space-bunny-alpha | — | closed stale | The multilayer CLI-configuration proposal was abandoned after support was deferred to a later iteration; no resolving PR or implementation reference was found. | |
| stealth/space-bunny-alpha | — | closed stale | Configuration-file support was deferred: maintainers narrowed the first pass to a local charmcraft.yaml, then closed the layered proposal without a resolving PR or commit. | |
| stealth/space-bunny-alpha | — | closed stale | The layered config-file proposal appears abandoned: multiple-file support was deferred, and no implementation or closing reference was found. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed after scoping down to a single local charmcraft.yaml file. The initial multilayer proposal was superseded by a simplified single-file approach. | |
| qwen/qwen3.6-35b-a3b | — | — | Implemented initial config file support using a single local charmcraft.yaml. Multilayer merging, user/system paths, and advanced option handling were deferred. The feature was integrated into charmcraft. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The multi-layer YAML configuration request was scoped to a single local file during discussion but ultimately abandoned or superseded by later tooling updates. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved by implementing YAML config file support, initially scoped to a single local file. Subsequent discussions refined merging precedence, added component metadata, and aligned with evolving project standards before closure. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.