Commit dab59c59 authored by Alex Kakiris's avatar Alex Kakiris
Browse files

configure static CCF endpoint paths

parent 8eb04627

README.md

+1 −0
Changes for README.md: 1 added line, 0 removed lines.
Original line number Diff line number Diff line
@@ -17,6 +17,7 @@ Notes: 
- Even when deploying OpenCAPIF, you should ensure local name resolution for capifcore, register, and vault in /etc/hosts based on your OpenCAPIF deployment configuration. This is required both to reach the services and to avoid certificate validation issues.

- If you use the default local OpenCAPIF deployment, no value changes are usually needed.

- If any of those service names are changed in your OpenCAPIF deployment, you must update docker-compose.yml accordingly (for example CAPIF_HOSTNAME, REGISTER_HOSTNAME, VAULT_HOSTNAME, and extra_hosts). This will be improved in future versions.

- CCF_ONBOARDING_URL, CCF_API_ONBOARDING_URL, CCF_PUBLISH_URL, CCF_DISCOVER_URL, and CCF_SECURITY_URL are static per deployment and must match the ccf_* paths returned by CAPIF's /getauth response; a mismatch is logged as a WARNING on login.



Example /etc/hosts entries for a default local setup:

docker-compose.yml

+6 −0
Changes for docker-compose.yml: 6 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -16,6 +16,12 @@ services: 
      - vault:host-gateway

    environment:

      - CAPIF_HOSTNAME=capifcore

      - PYTHONUNBUFFERED=1

      - CCF_ONBOARDING_URL=api-invoker-management/v1/onboardedInvokers

      - CCF_API_ONBOARDING_URL=api-provider-management/v1/registrations

      - CCF_PUBLISH_URL=published-apis/v1/<apfId>/service-apis

      - CCF_DISCOVER_URL=service-apis/v1/allServiceAPIs?api-invoker-id=

      - CCF_SECURITY_URL=capif-security/v1/trustedInvokers/<apiInvokerId>

      # - VAULT_HOSTNAME=vault.ocf-vault.svc.cluster.local # direccion VAULT despliegue

      - VAULT_HOSTNAME=host.docker.internal # direccion VAULT local

      - REGISTER_HOSTNAME=register:8084