launchdarkly_user_segment_sync – Sync LaunchDarkly User Segments across Environments

New in version 0.1.0.

Synopsis

  • Sync LaunchDarkly User Segments across Environments

Parameters

Parameter Choices/Defaults Comments
api_key
string / required
LaunchDarkly API Key. May be set as LAUNCHDARKLY_ACCESS_TOKEN environment variable.
environment_key
string / required
A unique key that will be used to determine source environment.
environment_targets
list / required
A list of environments that flag settings will be copied to.
excludedActions
list
    Choices:
  • updateTargets'
  • updateRules
Manage a list of excluded actions for copying.
includedActions
list
    Choices:
  • updateTargets
  • updateRules
Manage a list of included actions for copying.
project_key
string
Default:
"default"
Project key to look for flag
user_segment_key
string / required
A unique key that will be used to reference the user segment in this environment.

Examples

# Sync a LaunchDarkly User Segment to multiple environments
- launchdarkly_user_segment_sync:
    environment_key: test-environment-1
    environment_targets:
        - dev
        - staging
        - production
    name: "Test Segment"
    includedActions:
      - updateOn
      - updateRules

Status

  • This is not guaranteed to have a backwards compatible interface. [preview]

  • This is maintained by the Ansible Community. [community]

Hint

If you notice any issues in this documentation, you can edit this document to improve it.

Hint

Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.