launchdarkly_feature_flag_sync – Sync LaunchDarkly Feature Flags across Environments¶
New in version 0.1.0.
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.
|
|
excluded_actions
list
|
|
Manage a list of excluded actions for copying.
|
flag_key
string
/ required
|
A unique key that will be used to reference the user segment in this environment.
|
|
included_actions
list
|
|
Manage a list of included actions for copying. If not specified all actions are included.
|
project_key
string
|
Default: "default"
|
Project key to look for flag
|
Examples¶
# Sync a LaunchDarkly Feature Flag Configuration across environments
- launchdarkly_feature_flag_sync:
environment_key: test-environment-1
environment_targets:
- dev
- staging
- production
flag_key: test_flag_1
project_key: test_project
included_actions:
- updateOn
- updateRules
Return Values¶
Common return values are documented here, the following are the fields unique to this :
Key | Returned | Description |
---|---|---|
feature_flag
dictionary
|
on success |
Dictionary containing a Feature Flag
|
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.