manifest.yml

# Pushes the packaged console, not the source tree. Build it first:
#
#   make build release cf
#
# That stages dist/cf-package (jetstream binary, compiled ui/, config.properties,
# Procfile) and writes its own manifest alongside; this file is the equivalent for
# pushing that staged directory from the repo root. There is no build during
# staging, which is why binary_buildpack is enough. 512M matches what
# production deployments run; the 1024M disk leaves room for log growth.
applications:
  - name: console
    memory: 512M
    disk_quota: 1024M
    host: console
    timeout: 180
    path: dist/cf-package
    buildpack: binary_buildpack
    command: ./jetstream
    health-check-type: port
    env:
      # FWT-934: enable admin-gated /pp/v1/admin/diagnostics endpoint so we can
      # observe CF-call counts + timings under real adepttech traffic. Off by
      # default in production; adepttech is the test environment.
      DIAGNOSTICS_ENABLED: "true"
#    env:
# Override CF API endpoint URL inferred from VCAP_APPLICATION env 
#       CF_API_URL: https://CLOUD_FOUNDRY_API_ENDPOINT
# Force the console to use secured communication with the Cloud Foundry API endpoint
#       CF_API_FORCE_SECURE: true
# Turn on backend debugging
#       LOG_LEVEL: debug
# Tune CAPI list-pagination (see build-and-packaging.md "Runtime tuning")
#       STRATOS_CF_PER_PAGE: 1000
#       STRATOS_CF_MAX_PARALLEL_PAGES: 8

# User provided services can also be used to set environment properties:
#   env:
#     CF_UPS_NAME: stratos-properties
#   services:
#   - stratos-properties
# cf create-user-provided-service stratos-properties -p '{"CF_CLIENT":"stratos","CF_CLIENT_SECRET":"xxxx"}'