subiquity

Commit Graph

Author	SHA1	Message	Date
Dan Bungert	a0e2e244bd	add setting policy for post-install updates via autoinstall (#920 ) * Add element updates (non-UI) This can be controlled with autoinstall updates: security or all Also an API for controlling this: curl --silent --unix-socket .subiquity/socket a/updates -> "security" curl -d '"all"' --unix-socket .subiquity/socket a/updates * Automated tests - log grep for default/none/all states * Enforce possible values on Updates controller Route all the various get/set thru 2 common functions. Validate incoming data.	2021-03-31 13:57:53 -06:00
Dan Bungert	2c6474f3cb	Lock in current schema Accidental schema updates are unintended, so enforce that. Schema updates that don't break API are fine, we can handle that by manually regenerating the schema at such time.	2021-03-03 11:31:04 -07:00

Author

SHA1

Message

Date

Dan Bungert

a0e2e244bd

add setting policy for post-install updates via autoinstall (#920 )

* Add element updates (non-UI)

This can be controlled with autoinstall
updates: security or all

Also an API for controlling this:
curl --silent --unix-socket .subiquity/socket a/updates ->
"security"
curl -d '"all"' --unix-socket .subiquity/socket a/updates

* Automated tests - log grep for default/none/all states

* Enforce possible values on Updates controller

Route all the various get/set thru 2 common functions.
Validate incoming data.

2021-03-31 13:57:53 -06:00

Dan Bungert

2c6474f3cb

Lock in current schema

Accidental schema updates are unintended, so enforce that.  Schema
updates that don't break API are fine, we can handle that by manually
regenerating the schema at such time.

2021-03-03 11:31:04 -07:00

2 Commits