launchdarkly_webhook – Manage LaunchDarkly Webhooks

New in version 0.1.0.

Synopsis

• Manage LaunchDarkly Webhooks

Parameters

Parameter	Choices/Defaults	Comments
api_key string / required		LaunchDarkly API Key. May be set as LAUNCHDARKLY_ACCESS_TOKEN environment variable.
enabled boolean	Choices: no yes	Whether this webhook is enabled or not.
name string		A human-readable name for your webhook.
secret string		If sign is true, and the secret attribute is omitted, LaunchDarkly will automatically generate a secret for you.
sign boolean	Choices: no yes	If sign is false, the webhook will not include a signature header, and the secret can be omitted.
state -	Choices: absent present ←	Indicate desired state of the resource.
url string		The URL of the remote webhook.
webhook_id string		Webhook id. Required when updating resource.

Examples

# Create a new LaunchDarkly Webhook
- launchdarkly_webhook:
    state: present
    project_key: test-project-1
    environment_key: test-environment-1
    user_segment_key: test-key-1
    name: "Test Segment"
    description: "This is a testing segment"
    rules:
        clauses:
          - attribute: testAttribute
            op: contains
            values:
              - 2
              - 3
            negate: true
    tags:
      - blue
      - green
    included:
      - test1
      - test2
    excluded:
      - test3
      - test4

Return Values

Common return values are documented here, the following are the fields unique to this :

Key	Returned	Description
webhook dictionary	on success	Dictionary containing a Webhook

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.