Skip to content

LaunchDarkly (Independent Publisher)#4142

Open
aaronmahbuild wants to merge 2 commits intomicrosoft:devfrom
aaronmahbuild:connector/launchdarkly
Open

LaunchDarkly (Independent Publisher)#4142
aaronmahbuild wants to merge 2 commits intomicrosoft:devfrom
aaronmahbuild:connector/launchdarkly

Conversation

@aaronmahbuild
Copy link
Copy Markdown

@aaronmahbuild aaronmahbuild commented Mar 6, 2026

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I attest that I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.
  • I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
  • Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
  • Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

LaunchDarkly — Independent Publisher Connector

Overview

LaunchDarkly is a feature management platform that enables teams to safely deploy, control, and measure software features in production. This connector allows Power Automate users to manage feature flags, projects, and environments — creating flags, toggling them on and off, checking statuses, copying configurations between environments, and monitoring changes through the audit log. It enables automated feature flag management as part of CI/CD and operational workflows.

Publisher

Aaron Mah

Operations (13 total)

Operation Type Description
List Projects Action List all projects in your LaunchDarkly account
Get Project Action Get the details of a single LaunchDarkly project
List Feature Flags Action List all feature flags in a LaunchDarkly project
Get Feature Flag Action Get details of a single feature flag including per-environment configuration
Create Feature Flag Action Create a new feature flag in a LaunchDarkly project
Turn Flag On Action Turn on targeting for a feature flag in a specific environment
Turn Flag Off Action Turn off targeting for a feature flag in a specific environment
Delete Feature Flag Action Permanently delete a feature flag from a project
Copy Flag Configuration Action Copy a feature flag's configuration from one environment to another
Get Flag Status Action Get the status of a feature flag in a specific environment
List Environments Action List all environments in a LaunchDarkly project
Get Environment Action Get the details of a single environment in a project
List Audit Log Entries Action List recent audit log entries for your LaunchDarkly account

Authentication

API Key — LaunchDarkly personal access token with Writer role, passed via Authorization header.

Test Results

  • 13/13 operations tested successfully in Power Automate environment
  • Swagger validation passed (paconn validate equivalent, exit code 0)
  • 4 end-to-end scenario flows validated in Power Automate

Test Tab — All Operations

All operations passed

Scenario Flows

Scenario 1: Weekly Flag Health Report
Recurrence → List Projects → List Feature Flags → Get Flag Status → Compose → Post to Teams channel

Scenario 1 Run Success

Scenario 2: Feature Flag Request
Recurrence → List Environments → Create Feature Flag → Get Feature Flag → Compose → Post to Teams channel

Scenario 2 Run Success

Scenario 3a: Maintenance Start (Turn Flag Off)
Recurrence → Turn Flag Off → Get Flag Status → Compose → Post to Teams channel

Scenario 3a Run Success

Scenario 3b: Maintenance End (Turn Flag On)
Recurrence → Turn Flag On → Get Flag Status → Compose → Post to Teams channel

Scenario 3b Run Success

Notable Implementation Details

  • Semantic Patch Operations: The Turn Flag On / Turn Flag Off operations use LaunchDarkly's Semantic Patch format. APIM policy templates in apiProperties.json handle the Content-Type: application/json; domain-model=launchdarkly.semanticpatch header and route requests to the correct PATCH endpoint via routerequesttoendpoint and setheader policies.
  • No OAuth: Uses a simple API key (personal access token) — no app registration required.

@aaronmahbuild aaronmahbuild marked this pull request as ready for review March 12, 2026 22:27
@aaronmahbuild aaronmahbuild requested a review from a team as a code owner March 12, 2026 22:27
@vmanoharas
Copy link
Copy Markdown
Contributor

Hi @aaronmahbuild,

Thank you for submitting the connector. However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants