Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Epic Link:
-
Team:SQuaRE
-
Urgent?:No
Description
The request from the DFs is for the list of TAP servers presented in the portal interface to be configurable via phalanx so that it can be managed on a per-environment basis.
We propose this is achieved by allowing that list to be a java property (if it isn't already) and then we inject it in the chart via the existing mechanism - for an example see:
https://github.com/lsst-sqre/charts/blob/master/charts/firefly/templates/deployment.yaml#L62
(that is assuming that key-value pairs are sufficient for this - ask if you need more complex data structures)
Attachments
Issue Links
- duplicates
-
DM-31444 Portal application: devise a means to configure the list of known TAP servers without rebuilding the Portal/suit container image
- In Progress
Activity
Currently the default TAP-server list lives on the client (JavaScript) side of the application. I'll talk to Loi Ly about how we could get this information from the Firefly server to the client.
"Portal" team?