Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Adding the Sealights java agent into you Pivotal Cloud Foundry / VMWare Tanzu Application Services is done by using the standard java buildpack and configured in the following way:

Option A: In the manifest.yml of your app add the cloudfoundry java-buildpack

---
applications:
-  name: yourApp
    buildpacks:
    - https://github.com/cloudfoundry/java-buildpack

Option B: Add the buildpack through the command line

cf push -b https://github.com/cloudfoundry/java-buildpack

Once done, in order to add Sealights you need to do the following step:

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: '{lab_id: yourLabId}' 
  • pass them as environment variables for the application:

    cf set-env [my-application] JBP_CONFIG_SEALIGHTS_AGENT: '{lab_id: myLabId}'

​The available configuration keys are documented here:
Sealights java-buildpack configuration

Offline buildpack

If you need to create an offline buildpack without network access you can do so following the instructions here: https://github.com/cloudfoundry/java-buildpack#offline-package

  • No labels