...
- "File Manager" service should have a custom start-up process that differs from a normal stack
- User logs into NDS Labs UI
- User presses "Browse Files", which hits a new "/api/browse" REST endpoint
- API server checks for running file manager
- if no file manager is found, one is started
- User is directed to their running file manager UI
- See
Jira server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-441 - See
Jira server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-442
- Is the "File Manager" just a spec?
- There is no reason why this cannot be a spec
- We may want to hide this in the UI, if it would be trivial
- See
Jira server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-443
- Is the "File Manager" spec hidden in the catalog view?
- Given our "custom start" proposed above, we don't need to show this in the catalog
- That said, there is no harm in showing this in the catalog
- Spec can be found below
- authentication?
- we will look into doing this at the ingress level
- See
Jira server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-308
...