User based system wide service preferences

[mguidon]

Some applications have user preferences. We should store them as a file somewhere in S3 ,inject them via dynamic sidecar into the user services and store them back when the applications stops. Destination inside the container could be defined docker image label.

Tasks

Preview Give feedback

1. base functionality and backedn integration exposed to the stack
2. frontend integration of user based preferences #1062
   +0
   
3. user services integration

[GitHK]

System wide user preferences. Implementation notes.

• Data should be stored in Postgres as an object and should be easily accessible via a query
• There are a few settings which might come from the platform and some which might come from the service
• settings are serialised to a json object, that the user can modify and are passed to the service
• a service can freely add or remove a field from this model. adding and removing will result in adding or removing inside the db
• what happens if the preferences do not validate? do we keep the service hanging. Might be worth while to have this skippable via cli tools when closing.
• ideally these will be exposed in the fronted under the "preferences" tab form where the user can change them globally

Draft of the model stored in the DB

{
  # this is managed internally by osparc to associate the preference to the service
  "service_key": "dy-/s4l-dy",# used by oSPARC to inject in the field in this setting
  "property_type": "service|platform", # service are defined by each service, while platform is defined by oSPARC and will be available and visible to everybody, these can only be changed from the user interface
  
  # these are the only ones the service will see
  "prererence_id":"unique_identifier_for_this_service",# used by the platform to store them
  "writable": "true/false",# if the service is allowed to change any of the fields below
  "last_changed_utc_timestamp": "123132",# integer contains the last date time when this was changed, helpful when merging back the data(the latest one will be used when merging the fields below
  "value": "content",# content of the property

  # these are defined for the sake of he fronted to render the preference properly
  "visible_to_user": "true/false", # if will e shown in the frontend
  "render_as": "str|bool", # used by the frontend to display the "value" as type
  "display_label": "setting name", # label 
  "help_message": "some extra" # more info about the preference displayed as tooltip
}

[GitHK]

@mguidon can I close this case? Have you managed to save the preferences inside the service as well?

[mguidon]

We can close it. I think the problem is on my side. If not I will open another issue.