launchdarkly_custom_role – Manage LaunchDarkly Custom Roles

New in version 0.1.0.

Synopsis

• Manager LaunchDarkly Custom Roles

Parameters

Parameter		Choices/Defaults	Comments
api_key string / required			LaunchDarkly API Key. May be set as LAUNCHDARKLY_ACCESS_TOKEN environment variable.
description string			Description of the custom role
key string / required			Unique key to identify Custom Role
name string			A human-readable name for your webhook
policies dictionary / required			Policies to attach to the role
	actions string		Identify actions of policy
	effect string	Choices: allow deny	Defines whether the statement allows or denies access to the named resources and actions.
	not_actions string		inverse of actions for policy
	not_resources list		inverse of Resource to use in policy
	resources list		Resource to use in policy
state -		Choices: absent present ←	Indicate desired state of the resource

Examples

- launchdarkly_custom_role:
    state: present
    name: "My Custom Role"
    policies:
        resources:
          - "proj/*:env/*:flag/test_flag"
        actions:
          - "*"
        effect: allow

Return Values

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

Key	Returned	Description
custom_role dictionary	on success	Dictionary containing a Custom Role

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.