Means to reduce duplication of plugin fields
Metadata
Current evaluation
Maintainer-acknowledged request to support top-level YAML definitions and anchors for reusing repeated part source fields; implementation awaits upstream framework work tracked as CRAFT-2612.
Suggested action: keep open
Reason: A maintainer called this an "interesting idea," said it should apply to all craft applications, requested another maintainer's opinion, and linked internal ticket CRAFT-2612. The sample and error are reproducible, but no design decision or resolving commit exists; the loader already flattens YAML merge tags, while strict top-level validation still rejects the proposed definitions key.
Evaluated by: mr-cal-bot
Impact:
36
Quick Win:
11
Complexity:
58
Confidence:
91
Actionability:
74
Issue body
### What needs to get done
It could be handy if a recurring repo could be mentioned only once, for example:
```yaml
definitions:
kubeflow-source: &kubeflow-source
source: https://github.com/kubeflow/kubeflow
source-type: git
source-tag: v1.7-branch # upstream branch
source-depth: 1
parts:
backend:
plugin: nil
<<: *kubeflow-source
```
Currently this fails with:
```
Bad rockcraft.yaml content:
- extra field 'definitions' not permitted in top-level configuration
```
### Why it needs to get done
If the same repo+tag are used multiple times, it could be easier to maintain and easier to read.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
36
Quick Win:
11
Complexity:
58
Confidence:
91
Actionability:
74
|
keep open | Maintainer-acknowledged request to support top-level YAML definitions and anchors for reusing repeated part source fields; implementation awaits upstream framework work tracked as CRAFT-2612. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
9
Complexity:
55
Confidence:
68
Actionability:
70
|
keep open | Feature request to support YAML anchors/aliases via a top-level 'definitions' key in rockcraft.yaml to avoid repeating source/source-type/source-tag fields. Acknowledged by lengau, upstreamed to craft-application as CRAFT-2612; still unimplemented, awaiting cmatsuoka's feedback. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
11
Complexity:
40
Confidence:
70
Actionability:
60
|
keep open | Feature request to support YAML anchors/aliases in rockcraft.yaml for reducing duplication. Acknowledged by maintainer and transferred to upstream craft-application framework with Jira ticket CRAFT-2612 created. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
12
Staleness:
55
Complexity:
65
Confidence:
60
Support Request:
10
|
keep open | Feature request for a top-level 'definitions' section in craft app YAML to reduce duplication of recurring repo/source fields via anchors. Transferred to craft-application; maintainer sought opinion on approach (similar to grammar changes) in March 2024, no resolution since. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
10
|
close stale | Feature request to support YAML anchors and aliases in rockcraft.yaml for reducing plugin field duplication. Transferred to upstream craft-application framework over a year ago with an internal ticket created. Currently inactive. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
45
Confidence:
75
Support Request:
10
|
needs triage | Feature request to support YAML anchors in rockcraft.yaml for reducing plugin field duplication. Acknowledged by maintainers and transferred to upstream craft-application, but remains unlabelled and inactive. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.