application-pcf.yml

# Unlike autoconfig, in PCF services are deployed to their own application server instance and have no context path (root).
# Each capability specific integration service has its own route which can be configured below.
# Presentation services are accessed via the gateway and do not require any configuration.
# Remember to include the name of the space in the route to avoid collisions.

pcf:
  domain: apps.pcf-v21.backbasepcf.com
  uri: ${pcf.space}.${pcf.domain}

bb-fuel:
  platform:
    registry: http://registry-${pcf.uri}/eureka
    identity: http://bbiam-${pcf.uri}
    gateway: http://gateway-${pcf.uri}/api
    auth: ${bb-fuel.platform.gateway}/auth/login
    tokenconverter: http://token-converter-service-${pcf.uri}
  dbs:
    approvals: http://approval-integration-service-${pcf.uri}
    transactions: http://transaction-integration-service-${pcf.uri}
    contactmanager: http://contactmanager-integration-service-${pcf.uri}
    messages: http://messages-integration-service-${pcf.uri}
    user: http://user-integration-service-${pcf.uri}
    legalentity: http://legalentity-integration-service-${pcf.uri}
    accessgroup: http://accessgroup-integration-service-${pcf.uri}
    arrangements: http://arrangements-integration-service-${pcf.uri}
    notifications: http://notifications-presentation-service-${pcf.uri}