canonical / canonical/craft-application
Means to reduce duplication of plugin fields
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14
- Forks
- 29
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 12
Description
What needs to get done
It could be handy if a recurring repo could be mentioned only once, for example:
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the shown validation error with the rockcraft.yaml example, then trace how top-level configuration and parts fields are validated. Done means a recurring repository definition can be declared once and reused for parts without the extra-field error, while existing configuration validation continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100