LaunchDarkly

LaunchDarkly

This connector works with LaunchDarkly feature management through its REST API (https://app.launchdarkly.com/api/v2, API version 20240415): projects and environments, feature flags with their state and evaluation status, segments, metrics and experiments, the audit log, members and teams. It can create flags and segments, turn flags on or off, and change targeting with semantic patch instructions.

Setup (2 minutes)

1. In LaunchDarkly open Organization settings, Authorization (https://app.launchdarkly.com/settings/authorization) and create an access token. For reading choose the Reader role; to toggle and change flags Writer (or a custom role limited to the projects and environments the agent may change). A service token is not tied to a person.
2. Copy the token (api-..., shown once) into LAUNCHDARKLY_API_TOKEN and run launchdarkly_get_caller_identity to check it.
3. On the EU instance or the federal one, change the connector base URL to https://app.eu.launchdarkly.com or https://app.launchdarkly.us.

Workflow

• Find things: launchdarkly_list_projects, launchdarkly_get_project, launchdarkly_list_environments, launchdarkly_get_environment; then launchdarkly_list_flags with env: production and filter: query:checkout, and launchdarkly_get_flag for its targeting.
• Is a flag still used: launchdarkly_list_flag_statuses and launchdarkly_get_flag_status (inactive or launched flags are candidates for clean-up).
• Release: launchdarkly_create_flag, then launchdarkly_toggle_flag per environment; change targeting or rollout with launchdarkly_update_flag (use dry_run: true to preview). Retire a flag with archiveFlag in launchdarkly_update_flag; launchdarkly_delete_flag removes it for good.
• Audiences: launchdarkly_list_segments, launchdarkly_get_segment, launchdarkly_create_segment, launchdarkly_update_segment.
• Experiments: launchdarkly_list_metrics, launchdarkly_get_metric, launchdarkly_list_experiments, launchdarkly_get_experiment.
• Who changed what: launchdarkly_list_audit_log (e.g. spec: proj/default:env/production:flag/new-checkout) and launchdarkly_get_audit_log_entry. People: launchdarkly_list_members, launchdarkly_get_member, launchdarkly_list_teams, launchdarkly_get_team.

Switched off at install: launchdarkly_delete_flag; it cannot be undone, so an admin switches it on when the team needs it.

Before writing: toggling a flag or changing its targeting in production changes what live users get within seconds. Confirm the project, environment and flag with the user first, and add a comment (some environments require one; approval-gated environments answer 405 and need an approval request in the app).

Semantic patch: launchdarkly_toggle_flag, launchdarkly_update_flag and launchdarkly_update_segment send instructions such as {"kind": "addTargets", "contextKind": "user", "values": ["key-1"], "variationId": "<_id>"}. Variation, rule and clause ids are the _id fields from launchdarkly_get_flag or launchdarkly_get_segment. Rollout weights are in thousandths of a percent (100000 = 100%).

Reading the answers: keys (project, environment, flag, segment) are what you pass on; member and audit log ids are 24-character hex strings. Dates are Unix milliseconds (creationDate, lastModified, date). In a flag, environments.<key>.on says whether targeting is on and _summary.variations what is served. Environment SDK and mobile keys are left out of the answers.

Paging: lists take limit and offset and return totalCount and _links.next while more pages exist. The audit log returns at most 20 entries; page back with before set to the date of the last entry.

Errors: 401 means a wrong or deleted token, 403 a token whose role does not allow the call, 404 an unknown key, 400 or 409 an invalid patch or a conflicting change (the message names the problem), 405 a change that needs approval, 429 the rate limit (wait for the time in X-Ratelimit-Reset).