Since the data lake operates independently, we don't need to store its settings on the central server. However, we do need to store a user's draft for all modules.
Given this change, I suggest we remove all fields regarding the data lake in NodeSettings, except for the boolean giganto field indicating whether the data lake is supposed to run or not. Additionally, we should create another data structure, GigantoSettings, and add a new field, giganto_settings_draft, to Node to store the user's input for the data lake's settings.
Since the data lake operates independently, we don't need to store its settings on the central server. However, we do need to store a user's draft for all modules.
Given this change, I suggest we remove all fields regarding the data lake in
NodeSettings
, except for the booleangiganto
field indicating whether the data lake is supposed to run or not. Additionally, we should create another data structure,GigantoSettings
, and add a new field,giganto_settings_draft
, toNode
to store the user's input for the data lake's settings.