loomis
commented
6 years ago @schaubl I've made changes both to the client and server in relation to my previous comments. The attributes with the CIMI resources should be camel case, so this should be changed throughout the migration script. Also the terminology should be brought in line with the current vocabulary, for example, the 'prerecipe' workflow script should be changed to 'preinstall'.
Deeper questions on the resource organization:
- Should the module metadata be repeated in both the module and moduleVersion resources? It seems like this should only be needed in the module resource, unless we want to search for versions based on the metadata or keep versions of the metadata itself.
- Are the name, parent, and path all necessary? These require consistent values which may be broken if people can just edit the resource. It would probably better just to have "path", from which the others can be derived dynamically when necessary.
- Should the module resource contain anything other than the module metadata and the list of versions? It seems like the module schema can be reduced to just common metadata, module metadata, and the list of versions.
- Can the list of versions be empty? E.g. for a project where we don't duplicate the metadata. If so, the schema should be updated to make the list of versions optional.
schaubl
First version of the module migration script.
Connected to slipstream/SlipStream#292