.env – nocin.eu

In your mta.yaml you can define environment variables, which are filled during deployment. They can be filled with MTA Development and Deployment Parameters. Click here for an overview.

To get the URL of your deployed CAP service, simply use the ${default-url} parameter and pass the value to a variable below the properties attribute, e.g. SRV_URL. The approuter has to provide its default-url, which can then be used in the service for a variable, e.g. APPROUTER_URL.

  #####################################################################################################################
  # Approuter
  #####################################################################################################################
  - name: approuter
    type: approuter.nodejs
    path: app/approuter
    provides: 
      - name: app-api 
        properties:
          app-url: ${default-url}   # <---------------------------- provides approuter url
          app-uri: ${default-uri}   # <---------------------------- provides approuter uri/hostname
          app-protocol: ${protocol} # <---------------------------- provides approuter protocol

  #####################################################################################################################
  # Business Service Module
  #####################################################################################################################
  - name: mySrv
    type: nodejs
    path: gen/srv
    requires:
      - name: app-api # <---------------------------------------- required to access the provided variables of the approuter
    properties:
      SRV_URL: ${default-url}
      APPROUTER_URL: ~{app-api/app-url}
      SUBSCRIPTION_URL: ~{app-api/app-protocol}://\${tenant_subdomain}-~{app-api/app-uri}

After deployment, you can now access the URL via process.env.SRV_URL in a service handler. During development, simply use the .env file to provide the SRV_URL value.

You can check all the variables via the BTP Cockpit: Subaccount → Space → Select application → User-Provided Variables

cds.requires.ECEmploymentInformation.[development].credentials.authentication=BasicAuthentication cds.requires.ECEmploymentInformation.[development].credentials.username=myUsername cds.requires.ECEmploymentInformation.[development].credentials.password=myPassword

{ "cds": { "ECEmploymentInformation": { "kind": "odata-v2", "model": "srv/external/ECEmploymentInformation", "credentials": { "[production]": { "destination": "sfsf" }, "[development]": { "url": "https://apisalesdemo2.successfactors.eu/odata/v2", "authentication": "BasicAuthentication", "username": "myUsername", "password": "myPassword", } } } } }

Tag: .env

[CAP] Get service and approuter URLs of your running CAP application in a service handler

[CAP] Set credentials in package.json via .env