Snyk API Token
: The authentication token from Snyk.Path
: Your additions to the path to find needed third party tools such as Gradle or Maven.Custom Endpoint
: The custom endpoint for Single Tenant setups instead of https://app.snyk.io.Allow unknown certificate authorities
: Disable certificate checks for SSL connections.Custom Snyk LS Path
: Specify the location of your language server binaries. If set, no updates are downloaded and updates must be performed manually to synchronize Eclipse features and preferences with the Language Server.Snyk Open Source enabled
: Enable/Disable Snyk Open Source Dependency Scans via Language Server. Default: Enabled
during betaSnyk Code enabled
: Enable/Disable Snyk Code Scans via Language Server. Default: Disabled
during beta.Snyk Infrastructure-as-Code enabled
: Enable/Disable Snyk IaC Scans via Language Server. Default: Enabled
during beta.Organization
: Specify the Snyk Organization to use for scanning.Additional Parameters
: Specify additional parameters to pass to the CLI (for example, --all-projects
or -d.
Additional Environment
: Add environment variables to Language Server.Send error reports to Snyk
: Send errors from Language Server to Snyk to enable quicker bug fixing. Default: Enabled
during beta.Send usage statistics to Snyk
: Allow Snyk to get usage data to improve workflows. Default: Disabled
during beta.PATH
: The path to needed binaries, for example, to Maven. The PATH
variable can also be manually adjusted using the Path
field in the settings dialog.JAVA_HOME
: The path to the JDK you want to use to analyze Java dependencieshttp_proxy
and https_proxy
: Proxy set using the value in the format http://username:[email protected]:proxyport
.
Note: the leading http://
in the value does not change to https://
for an https_proxy
.launchd
needs to know the environment variables to launch Eclipse directly from the Finder. Set these environment variables using the launchctl setenv
command (for example, on start up or using a script you launch at user login).
Note: Provision of environment variables to the macOS UI may change between operating system releases, so it can be easier to create a small shell script that launches the Eclipse app to leverage the shell environment. This can be defined via ~/.bashrc
./etc/environment
can be used to propagate the environment variables to the windows manager and UI.js
file: