JSON schema: improve non-storage parts

[mvidner]

Problem

While reviewing #1263 I read the whole schema and saw room for improvement. Small things

Solution

• disallow additional properties
• more specific type than string

Testing

Minimal, just making sure the schema itself is valid, by

$ agama profile validate rust/agama-lib/share/examples/profile_gnome.json
The profile is valid

[mvidner]

feature request: I am surprised that we don't allow hashed passwords in the profile

[imobachgs]

Yes, you are right, that's something we need to implement. I have created a placeholder card in Trello.

[coveralls]

coverage: 71.408%. remained the same
when pulling 945c670 on schema-nonstorage
into 7101d0d on master.

[coveralls]

coverage: 71.408%. remained the same
when pulling 945c670 on schema-nonstorage
into 7101d0d on master.

[mvidner]

BTW, here the examples feature really shines because it provides an alternative to the dense regexp

Unfortunately, agama profile validate does not check whether the schema is internally consistent and uses only valid examples. Like, I could use a number here and it would not notice.

[mvidner]

FIXME, need to look up in the code what is valid here

[mvidner]

@teclator can you advise please?
service/test/agama/autoyast/wireless_reader_test.rb and
web/src/components/network/WifiConnectionForm.jsx seem to have different sets of values

[imobachgs]

I did not know about the examples element. Thanks!

[imobachgs]

Yes, you are right, that's something we need to implement. I have created a placeholder card in Trello.

[imobachgs]

We support specifying the whole locale (en_US.UTF-8). If no encoding is given (e.g., en_US), we fall back to UTF-8.