"snap set" doesn't validate config option names
Bug #1805162 reported by
Vladimir Kiryakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
When we set snap options it's impossible to get just setted keys in configure script. We want to validate typo in option name and prevent snap user to set incorrect options.
Revision history for this message
| Paweł Stołowski (stolowski) wrote | #1 |
| no longer affects: | snappy |
| description: | updated |
| summary: |
- Impossible to get newly settled props + "snap set" doesn't validate config option names |
| Changed in snapd: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
To post a comment you must log in.
Yes, this is a known limitation and the long term plan is to implement configuration schemas where options will be constrained and invalid ones rejected.