Schema prevents user from specifying source-type local
Bug #1695886 reported by
Jonathan Cave
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
High
|
Jonathan Cave | ||
Bug Description
The recent change to the schema that added an enumeration of valid 'source-types' means that now you cannot specify source-type to be local.
The particular use case this allows is when you have a remote part with one of the currently valid source types e.g. git, and you want to fast iterate on the part without the requirement to check in to a repo (even one on your local file system). It was previously possible to override the source-type to local by putting any non-valid value in your local snapcraft.yaml source-type field whilst keeping all the other useful stuff like build-packages etc.
| Changed in snapcraft: | |
| assignee: | nobody → Jonathan Cave (jocave) |
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → In Progress |
| importance: | Undecided → High |
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #2 |
| Changed in snapcraft: | |
| status: | In Progress → Fix Committed |
| milestone: | none → 2.32 |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix here: https:/