Separating the plugin's options from the nomad.yaml file
It would be nice to separate ui/plugin options in the plugin and nomad.yaml. It would be nice to define ui > apps > options ...
in nomad_plugin.yaml.
- options' attribute of ui/plugin could be part of nomad_plugin.yaml file
- it would behave as defaults so you can still override with nomad.yaml
- nomad.yaml would mostly control exclude/include attribute
Use cases:
- @sbrueck 's use case: installing multiple plugins using in a nomad oasis installation. some of the plugins depends on python packages not available in the main image so a custom image needs to built which would contain all plugins and them configuration.
- @afekete 's use case: the support for jupyter notebooks will be implemented as an external parser but should be still part of the core nomad package. It would be nice to use the plugin's yaml file to store its configs instead of putting them as default values of the main configuration.