# LaunchDarkly

![LaunchDarkly-new-Logo.png](https://assets.relyanceuat.xyz/images/docs/5843835456397/20532325440397.png)
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:**

1. Login to your LaunchDarkly account.
2. In the left-hand navigation menu click **Account settings**.
3. In the dropdown box below the **Account settings** header, choose **Authorization**.
4. Click **Create token** in the **Access tokens** section.
5. Fill out the resulting dialog providing a meaningful name.
6. Click **Save token**.
7. Copy the **Access Token** to be used in Relyance.

![LaunchDarkly-3.png](https://assets.relyanceuat.xyz/images/docs/5843835456397/20532325444877.png)

![LaunchDarkly-4.png](https://assets.relyanceuat.xyz/images/docs/5843835456397/20532325450253.png)

**In the Relyance AI application:**

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **LaunchDarkly** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Oauth2 / App Token**.
8. Paste the **Access Token** into its respective field.

![LaunchDarkly-1.png](https://assets.relyanceuat.xyz/images/docs/5843835456397/20532325464333.png)

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

![LaunchDarkly-2.png](https://assets.relyanceuat.xyz/images/docs/5843835456397/20532349389709.png)

11. Congratulations, you are now connected to **LaunchDarkly**.

    The **Authentication** step asks for:

    - **Access Token**: required; held as a secret.

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## 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) | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). 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`.

```hcl
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 } }
}
```

<!-- terraform-examples:end -->