What to do when applying a config:
- if the product is unknown (invalid, missing):
- add product issue
- keeps the current config and proposal (if any)
- report 400
PUT: the config must indicate a valid product.
api.ts
/api/system
queries.ts
hooks/system.ts
hooks/l10n/system.ts
hooks/storage/system.ts
The new API is designed around 3 main concepts: system, config and proposal.
The config contains elements that can modify the system, the proposal or both. For example, the dasd config changes the system, and the storage config changes the proposal. In other cases like network, the config can affect to both system and proposal.
This document analyzes when Agama probes the system and what problems the current approach has, and proposes a possible solution.
In storage we have a JSON structure (model) and we need: