service: load maker, model and stream from config
For the longest time, we used stub values for the maker, model and stream
properties. With the recent drive to complete the online side of SystemOTA
we are now able to load the values from the configuration system at
startup.
Tests are adjusted to use the test-* prefix for the values, in order to
avoid missing stub values anywhere. Integration tests are modified to
measure the values which are now set in the prepare logic of the test
suite.
There's a missing bit of integration between the writable update stream
property and the configuration system. At the moment changes to that
property are lost.
The update server is not used yet. It is also not exposed in the API,
on purpose, so that it cannot be modified or even read before the
interface between the client and the server is implemented.
Signed-off-by:
Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
Showing
- cmd/sysotad/spread.suite/introspection/introspection-expected-debug.txt 32 additions, 32 deletions...read.suite/introspection/introspection-expected-debug.txt
- cmd/sysotad/spread.suite/introspection/introspection-expected-production.txt 25 additions, 25 deletions...suite/introspection/introspection-expected-production.txt
- cmd/sysotad/spread.suite/introspection/task.yaml 2 additions, 5 deletionscmd/sysotad/spread.suite/introspection/task.yaml
- cmd/sysotad/spread.suite/smoke/task.yaml 4 additions, 4 deletionscmd/sysotad/spread.suite/smoke/task.yaml
- service/service.go 3 additions, 3 deletionsservice/service.go
- service/service_test.go 14 additions, 10 deletionsservice/service_test.go
- spread.yaml 9 additions, 0 deletionsspread.yaml
Please register or sign in to comment