Routes configuration

This page contains the routes configuration to reach the different services offered by the Portal.

Routes configuration

The routes to the endpoints used for this project are defined as follows:

export class ConfigService {
  base: string = window.location.origin + "/api/v3/";
  register: string = "users/";
  login: string = "sessions/";
  services: string = "services";
  requests: string = "requests";
  instances: string = "records/services";
  licences: string = "licences/";
  packages: string = "packages";
  slaTemplates: string = "slas/templates";
  slaAgreements: string = "slas/agreements";
  guarantees: string = "slas/configurations/guaranteesList";
  functions: string = "functions";
  slicesTemplates: string = "slices";
  slicesInstances: string = "slice-instances";
  tests: string = "tests/descriptors";
  runtimePolicies: string = "policies";
}

Being the base route defined as the protocol, the domain name and the port number where the Portal is deployed plus the "/api/v3/" route to reach the endpoints offered by the tng-api-gk.

In case the Portal Service Platform or Service Management are launched locally, the base route will be changed automatically to reach the http://pre-int-sp-ath.5gtango.eu:32002/api/v3/ environment. In case it is the Portal V&V Platform the one launched locally, the default base route to be reached is http://pre-int-vnv-bcn.5gtango.eu:32002/api/v3/.