1. Create a User-Provided Service and configure it with an agent token. This should be done once, before configuring the first application.
A different name for the user-provided service may be used, but it has to include the word "sealights" (lowercase) for the integration to work
Linux:
cf cups sealights -p '{"token":"ey…"}'
Windows:
cf cups sealights -p "{\"token\":\"ey…\"}"
The token may later be changed using:
cf update-user-provided-service sealights -p ....
2. Bind the User-Provided Service with your application
cf bind-service [app name] sealights
3. If the build session id, lab id, proxy or other settings need to be configured, you may either:
hard-code them in manifest.yml:
env: JBP_CONFIG_SEALIGHTS_AGENT: '{build_session_id: c2e21d80-ad88-4ff9-9e81-57c781ac5fe6, lab_id: yourLabId, auto_upgrade: false, version: +}'pass them as environment variables for the application:
cf set-env [my-application] JBP_CONFIG_SEALIGHTS_AGENT: '{build_session_id: 5d4...00b4, lab_id: myLabId}'
The available configuration keys are documented here:
Sealights java-buildpack configuration