Skip to main content

update_target_feature_flag

Facts​

DescriptionUpdate a target in a feature flag
SchemaConnectors.LaunchDarkly.functions.UpdateTargetFeatureFlag
ServiceLaunchDarkly

Input parameters​

Required input parameters

environment_keystringRequired

The environment associated with this feature flag

Examples
env123-123abc
feature_flag_keystringRequired

The key of the feature flag to update

Examples
feature-123abc
kindstringRequired

The kind of target operation for this update

Accepted values
addTargetsremoveTargets
launchdarkly_access_tokenslack#/types/credential/oauth2Required

LaunchDarkly access token. See the authentication section for details.

project_keystringRequired

The key of the project in which the feature flag to update is located

Examples
project-key-123abc
target_keyarrayRequired

The target key associated with this update

Examples
feat-t3-abc987
variation_idstringRequired

The ID of the feature flag variation to associate with this feature flag, based on the project's defined feature flag variations

Examples
123abc

Optional input parameters

commentstringOptional

A comment associated with this update

context_kind_keystringOptional

The target type (e.g., the context) associated with the target operation

Output parameters​

Required output parameters

namestringRequired

Feature flag name

Optional output parameters

commentstringOptional

Update target comment

descriptionstringOptional

Feature flag description

environment_keystringOptional

Environment key

keystringOptional

Feature flag key

kindstringOptional

Target operation

Authentication​

End-user authentication

User workflows that include a connector function relying on end-user authentication can only be started with a link trigger.

{
  "launchdarkly_access_token": {
    "credential_source": "END_USER"
  }
}

End-user experience: User will be prompted to link their external account via OAuth when they first start the workflow that contains this connector.

Developer experience: Developer does not have to implement authentication in the app.

Usage info​

First, import Connectors from deno-slack-hub into your project's import_map.json file, like this:

import_map.json
{
    "imports": {
      "deno-slack-hub/": "https://deno.land/x/deno_slack_hub@2.2.0/",
      "deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.14.2/",
      "deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/"
    }
  }

Next, import Connectors at the top of your workflow's definition file:

my_workflow_file.ts
import { Connectors } from "deno-slack-hub/mod.ts";

Finally, add the connector as a step in your workflow just like you would a Slack function.

my_workflow_file.ts
SomeWorkflow.addStep(
  Connectors.LaunchDarkly.functions.UpdateTargetFeatureFlag, {
  //...

🧙🏼 Your admin may need to approve the connector first. If your workspace has been configured to only allow admin-approved apps, the CLI will prompt you to send an admin approval request the first time you try to use a connector that hasn't been approved by an admin yet. While waiting for admin approval, the CLI may report an error like this:

Workflow function X is referring to an unknown step output parameter Y

You can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.