GPII-457: Adding better support for the cloud based flow manager , solutions registry and match maker. #171
Conversation
…registry and pref server.
|
@michelled, @kaspermarkus, and @amb26, what's the status of this pull request? It looks like something we should review and merge into master before @avtar does our final pre-review deployment. |
Conflicts: gpii/node_modules/flowManager/configs/base.json gpii/node_modules/flowManager/configs/cloudBased.json gpii/node_modules/flowManager/configs/development.json gpii/node_modules/flowManager/configs/production.json gpii/node_modules/preferencesServer/configs/base.json
| @@ -0,0 +1,12 @@ | |||
| { | |||
There was a problem hiding this comment.
This file appears to have been migrated from a .js form of the same views held in sgithens repository, as referenced in the JIRA. Could you add a text file in this directory explaining this relationship, and also explaining i) why the form of the view differs from the upstream version, ii) instructions for the integrating user in importing the views into CouchDB (or else scripts for this) and iii) an explanation of what our intended trajectory is for these files - are we intending to keep them in this JSON format or are we intending to adopt a framework to help with managing them?
Thanks
|
@amb26 Is this pull request still relevant? |
|
bumping - @amb26 Is this pull request still relevant? |
|
I think the only thing unique in this branch is the gpii-solutions.json view definition, and given that i) the solutions registry format has changed a little anyway ii) this came with no scheme for loading it into a database in any case, iii) this is something that @the-t-in-rtf has sufficient expertise now to easily reproduce, we can close this request |
No description provided.