Add /api/config/ to return mapr_settings.CONFIG as JSON

[will-moore]

This makes the mapr_settings.CONFIG available as JSON data, so it can be used by other apps.
E.g. ome/omero-gallery#25

To test:

• go to /mapr/api/config/ E.g. http://web-dev-merge.openmicroscopy.org/mapr/api/config/
• Should see JSON that corresponds to omero.web.mapr.config setting.

[will-moore]

@sbesson @manics How to get this deployed, tested & merged?
Currently I'm hard-coding this in ome/omero-gallery#25 until I can point at a server.

[manics]

@jburel Gallery is on web-dev-merge.openmicroscopy.org/gallery/ can we do the same for mapr?

[jburel]

certainly

[will-moore]

Added mapr to web-dev-merge.
See http://web-dev-merge.openmicroscopy.org/mapr/api/config/

[sbesson]

Functionally tested using the CI deployment. I can confirm the behavior as described in this PR i.e.

$ curl http://web-dev-merge.openmicroscopy.org/mapr/apnfig/
{"gene": {"default": ["Gene Symbol"], "all": ["Gene Symbol", "Gene Identifier"], "ns": ["openmicroscopy.org/mapr/gene"], "label": "Gene"}, "antibody": {"default": ["Antibody Identifier"], "all": ["Antibody Identifier"], "ns": ["openmicroscopy.org/mapr/antibody"], "label": "Antibody"}}

Generally, agreed that defining an endpoint to expose the mapr configuration is a useful addition especially in the case of public deployments like IDR. As discussed, the only caveat might be a case where part of the configuration contains secure information which should not be shared.

I do not have a use case in mind but it might be worth adding an extra configuration as a follow-up allowing the selective disabling of this endpoint.

In the interim, proposing to merge and cut a 0.3.0a1 release of omero-mapr to move forward with the deployment of the new IDR UI on the testing resource.