BN Map is incorrectly generated

[jrambla]

It seems that the BN is creating its own /map by aggregating the maps from the different beacon members.
However, this makes the BN map unstable as it depends on the beacons available (responding) at a given moment.
We created a mock endpoint "/gVariants2" and the BN picked it as its own genomicVariations endpoint.
I believe that the BN should have its own map and redirect the calls to the corresponding endpoints in the beacons.

[redmitry]

Yes. Beacon Network is a proxy / aggregator so it has no other endpoints apart of those that exist in backed beacons.
Beacon specification doesn't predefine endpoints (that's why the /map exists in a first place?) so /gVariants2 is perfectly valid.
Currently, it takes endpoints name from first found beacon and "links" other endpoints of the same type into it.

So the idea is to add "dummy" map configuration to map beacons' endpoints into predefined endpoint?

D.

[jrambla]

Yes,
IMU, the natural way is the BN to present its own map, that doesn't depend on having beacon instances up and running. Then, internally, the BN redirects every call to its endpoints to the beacon specific URLs.
I guess that the code is kind of doing that one way or another as every beacon could have a totally different path for the same concept.

[redmitry]

Implemented in the dev branch df1c388.

Basically one may put beacon-network-map.json template into the BEACON_NETWORK_CONFIG_DIR (or put in into the *.war file - should it be preconfigured by default???).

D.