LaunchDarkly
LaunchDarkly is a feature management platform that empowers companies to effectively control and release new features in their software applications. By integrating LaunchDarkly into your software development workflow, you can easily manage feature toggles and roll out updates, enabling safer, more efficient feature releases and experimentation for your applications.
In order to integrate LaunchDarkly with Relyance AI you will need an Access Token.
You will need a LaunchDarkly Pro subscription or better to use API controls.
In LaunchDarkly:
- Login to your LaunchDarkly account.
- In the left-hand navigation menu click Account settings.
- In the dropdown box below the Account settings header, choose Authorization.
- Click Create token in the Access tokens section.
- Fill out the resulting dialog providing a meaningful name.
- Click Save token.
- Copy the Access Token to be used in Relyance.


In the Relyance AI application:
- Login to your Relyance account.
- Navigate to the Settings Menu in the bottom left-hand side.
- Select Integrations.
- Click on the Vendor Integration tab.
- Find the LaunchDarkly integration card and click it to open its connections.
- Under Authentication Method, choose Oauth2 / App Token.
- Paste the Access Token into its respective field.

- Click Save.
- At this point, you should see the following result on the Vendor Integrations page:

Congratulations, you are now connected to LaunchDarkly.
The Authentication step asks for:
- Access Token: required; held as a secret.
Authentication methods and fields
Pick one of these under Authentication Method on the connection wizard's Authentication step. This table is generated from the integration catalog, so it always matches what the form actually asks for.
| Method | Required | Optional |
|---|---|---|
| Custom | Access Token (secret) |
— |
Manage this integration with Terraform
Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.
resource "relyance_integration_connection" "launchdarkly" {
vendor = "launchdarkly"
name = "<your connection name>"
auth = {
method = "access-token"
params = {
data_storage_location = "us"
}
# Secret fields are write-only: sent to Relyance, never stored in state.
secrets_wo = {
ACCESS_TOKEN = var.launchdarkly_access_token
}
secrets_wo_version = 1
}
scans = { "data-inspection" = { enabled = true } }
}