Wrong source-type in yaml is ignored
Bug #1650943 reported by
Leo Arias
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
Medium
|
Eduardo Vega | ||
Bug Description
When you are using an invalid source-type in snapcraft.yaml, it is ignored and no error is printed.
To reproduce, use a yaml with this in one part:
plugin: dump
source: .
source-type: nothing
It will successfully snap. I expect this to fail.
Revision history for this message
| Kyle Fazzari (kyrofa) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → Triaged |
| Changed in snapcraft: | |
| assignee: | nobody → Eduardo Vega (edvegavalerio) |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #2 |
| Changed in snapcraft: | |
| milestone: | none → 2.30 |
| status: | Triaged → Fix Committed |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Confirmed, it simply defaults to the `Local` source type if the `source-type` keyword is invalid. This should be validated by a custom type in the schema which compares against internal.