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 5 Next »

We’re sorry for the inconvenience but this page is under construction.
Please contact support in the meantime.

When deploying the application, the Sealights agent, which was embedded in the application via static instrumentation, will run when enabled.

To associate it to a lab that the tests run against, the Lab ID needs to be provided via a dedicated environment variable SEALIGHTS_LAB_ID

For example, you can use the following commands:

Dockerfile

ENV SEALIGHTS_LAB_ID=integ_test_myapp

Linux

export SEALIGHTS_LAB_ID=integ_test_myapp

Powershell

TBC

Standalone

TBC

Lambda

TBC

Additional Environment variables

The go agent sets the runtime configuration during the scan process. however, in some cases, there is a need to override the configuration parameters during runtime.

This can be done via environment variables as below:

Environment Variable Name

Default Value

Description

SEALIGHTS_DISABLE_ON_INIT

TRUE

You need to set this env variable to false in order to enable sealights when running the scan with --disable-on-init true

SEALIGHTS_DISABLE

TRUE

If you do not run the scan with --disable-on-init true, then use this flag to disable Sealights. (For instance in production)

SEALIGHTS_COLLECTOR_URL

““

Setting Collector URL in light mode (for lambda apps)

SEALIGHTS_LAB_ID

BuildSession Id

Setting Lab Id

SEALIGHTS_PROXY_URL

““

Proxy URL for connection to server

SEALIGHTS_LOG_LEVEL

info

Min log level: “debug", "info", "warn", "error"

SEALIGHTS_LIGHT_MODE

FALSE

Enable/Disable agent mode in light mode (for lambda apps)

  • No labels