You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is part of the effort to add functionality of a Data Center Registry to the Program Service:
The Program Service scope is being expanded to also act as a Data Center Registry. Data Centers represent the Regional Data Processing Centers (RDPC) that ARGO will support a network of. Each program registered in the program-service must belong to a single Data Center. The Data Centers have various connection details that also need to be stored.
Add REST Endpoint to fetch list of programs that are available within a specified Data Center.
Detailed Description
Request
GET /datacenters/{datacenter_short_name}/programs
Inputs
Parameter
Type
Required
Value
Description
datacenter_short_name
path
Yes
String
Short Name of a Data Center
Resposne
JSON Array of Programs that belong to the specified Data Center - Only publicly visible program data should be returned.
If the provided short name is not found in the Data Center table, return an error 404 not found.
Auth Rules
This endpoint is restricted to DCC Admins.
DCC Admin is identified by having WRITE permission for the Program Service system scope (ie. PROGRAMSERVICE.WRITE scope).
The text was updated successfully, but these errors were encountered:
Add REST Endpoint to fetch list of programs that are available within a specified Data Center.
Detailed Description
Request
GET /datacenters/{datacenter_short_name}/programs
Inputs
Resposne
JSON Array of Programs that belong to the specified Data Center - Only publicly visible program data should be returned.
If the provided short name is not found in the Data Center table, return an error 404 not found.
Auth Rules
This endpoint is restricted to DCC Admins.
DCC Admin is identified by having WRITE permission for the Program Service system scope (ie.
PROGRAMSERVICE.WRITE
scope).The text was updated successfully, but these errors were encountered: