v2.4.1

[2.4.1] (January 21, 2022)

BUG FIXES:

• Fixed a bug preventing launchdarkly_flag_triggers from being created in the enabled state.

• Fixed a bug introduced in v2.2.0 where launchdarkly_segments with rule blocks not containing a weight were defaulting to a weight of 0.

v2.4.0

[2.4.0] (January 19, 2022)

FEATURES:

• Added a launchdarkly_team_members data source to allow using multiple team members in one data source.

• Added a new launchdarkly_metric resource and data source for managing LaunchDarkly experiment flag metrics.

• Added a new launchdarkly_flag_triggers resource and data source for managing LaunchDarkly flag triggers.

• Added a new launchdarkly_relay_proxy_configuration resource and data source for managing configurations for the Relay Proxy's automatic configuration feature.

• Added a new launchdarkly_audit_log_subscription resource and data source for managing LaunchDarkly audit log integration subscriptions.

ENHANCEMENTS:

• Updated tests to use the constant attribute keys defined in launchdarkly/keys.go.

• Added a pre-commit file with a hook to alphabetize launchdarkly/keys.go

• Improved 409 and 429 retry handling.

v2.3.0

[2.3.0] (January 4, 2022)

FEATURES:

• Added default_client_side_availability block to the launchdarkly_project resource to specify whether feature flags created under the project should be available to client-side SDKs by default.

BUG FIXES:

• Fixed a bug in the launchdarkly_project and launchdarkly_environment resources which caused Terraform to crash when environment approvals settings are omitted from the LaunchDarkly API response.

NOTES:

• The launchdarkly_project resource's argument include_in_snippet has been deprecated in favor of default_client_side_availability. Please update your config to use default_client_side_availability in order to maintain compatibility with future versions.

• The launchdarkly_project data source's attribute client_side_availability has been renamed to default_client_side_availability. Please update your config to use default_client_side_availability in order to maintain compatibility with future versions.

v2.2.0

[2.2.0] (December 23, 2021)

ENHANCEMENTS:

• Upgraded the LaunchDarkly API client to version 7.
• Flag resource creation respects project level SDK availability defaults.

FEATURES:

• Added client_side_availability block to the launchdarkly_feature_flag resource to allow setting whether this flag should be made available to the client-side JavaScript SDK using the client-side ID, mobile key, or both.

NOTES:

• The launchdarkly_feature_flag resource's argument include_in_snippet has been deprecated in favor of client_side_availability. Please update your config to use client_side_availability in order to maintain compatibility with future versions.

v2.1.1

[2.1.1] (October 11, 2021)

BUG FIXES:

• Fixed an oversight in the approval settings where the environment approval_settings property can_apply_declined_changes was defaulting to false where it should have been defaulting to true in alignment with the LaunchDarkly API.

• Updated an error message.

v2.1.0

[2.1.0] (October 8, 2021)

FEATURES:

• Added approval_settings blocks to the launchdarkly_environment resource and nested environments blocks on the launchdarkly_project resource.

• Added a boolean archive attribute on the launchdarkly_feature_flag resource to allow archiving and unarchiving flags instead of deleting them.

v2.0.1

BUG FIXES:

• Fixed a bug resulting in nested environments not being imported on the launchdarkly_project resource. As a result, all of a project's environments will be saved to the Terraform state during an import of the launchdarkly_project resource. Please keep in mind if you have not added all of the existing environments to your Terraform config before importing a launchdarkly_project resource, Terraform will delete these environments from LaunchDarkly during the next terraform apply. If you wish to manage project properties with Terraform but not nested environments consider using Terraform's ignore changes lifecycle meta-argument.

v2.0.0

ENHANCEMENTS:

• Improved test coverage.

NOTES:

• As part of the ongoing deprecation of Terraform 0.11, the LaunchDarkly provider now only supports Terraform 0.12 and higher.

• This release changes the way LaunchDarkly recommends you manage launchdarkly_environment and launchdarkly_project resources in tandem. It is recommended you do not manage environments as separate resources unless you wish to manage the encapsulating project externally (not via Terraform). As such, at least one environments attribute will now be Required on the launchdarkly_project resource, but you will also be able to manage environments outside of Terraform on Terraform-managed projects if you do not import them into the Terraform state as a configuration block on the encapsulating project resource.

• The deprecated launchdarkly_destination resource enabled field has been removed in favor of on. on now defaults to false when not explicitly set.

• The default_on_variation and default_off_variation properties on the launchdarkly_feature_flag resource have now been replaced with a computed defaults block containing the properties on_variation and off_variation that refer to the variations in question by index rather than value.

• The launchdarkly_feature_flag_environment resource and data source target attribute schema has been modified to include a new variation attribute. Here variation represents the index of the feature flag variation to serve if a user target is matched.

• The deprecated launchdarkly_feature_flag_environment resource targeting_enabled field has been removed in favor of on. on now defaults to false when not explicitly set.

• The deprecated launchdarkly_feature_flag_environment resource user_targets field has been removed in favor of targets. targets now defaults to null when not explicitly set.

• The deprecated launchdarkly_feature_flag_environment resource flag_fallthrough field has been removed in favor of fallthrough.

• The deprecated launchdarkly_webhooks resource enabled field has been removed in favor of on. on is now a required field.

• The deprecated launchdarkly_webhooks resource policy_statements field has been removed in favor of statements.

• off_variation and fallthrough (previously flag_fallthrough) on launchdarkly_feature_flag_environment are now Required fields.

• Most optional fields will now be removed or revert to their null / false value when not explicitly set and / or when removed, including:

  • on on the launchdarkly_destination resource

  • include_in_snippet on the launchdarkly_project resource

  • on the launchdarkly_environment resource and in environment blocks on the launchdarkly_project resource:

    • secure_mode

    • default_track_events

    • require_comments

    • confirm_changes

    • default_ttl (reverts to 0)

  • on the launchdarkly_feature_flag_environment resource:

    • on (previously targeting_enabled, reverts to false)

    • rules

    • targets (previously user_targets)

    • prerequisites

    • track_events (reverts to false)

BUG FIXES:

• Fixed a bug in the launchdarkly_webhook resource where statements removed from the configuration were not being deleted in LaunchDarkly.

• The launchdarkly_feature_flag resource maintainer_id field is now computed and will update the state with the most recently-set value when not explicitly set.

• The client_side_availability attribute on the launchdarkly_feature_flag and launchdarkly_project data sources has been corrected to an array with a single map item. This means that you will need to add an index 0 when accessing this property from the state (ex. client_side_availability.using_environment_id will now have to be accessed as client_side_availability.0.using_environment_id).

v1.7.1

BUG FIXES:

Fixes a bug where attempts to create resource_launchdarkly_feature_flag variations with an empty string value were throwing a panic.
NOTES:

The launchdarkly_feature_flag_environment resource and data source's flag_fallthrough argument has been deprecated in favor of fallthrough. Please update your config to use fallthrough in order to maintain compatibility with future versions.

The launchdarkly_feature_flag_environment resource and data source's user_targets argument has been deprecated in favor of targets. Please update your config to use targets in order to maintain compatibility with future versions.

v1.7.0

FEATURES:

• Added the creation_date attribute to the launchdarkly_segment data source and resource.

ENHANCEMENTS:

• Upgraded the Terraform plugin SDK to v1.17.2.

• Upgraded the LaunchDarkly API client to v5.3.0.

• Added example team member resource configs in examples/team_member.

BUG FIXES:

• Updated the project_key attribute on the environment resource to be Required in keeping with the API.

• Added validation for launchdarkly_access_token resource creation and updates.

• Fixed a bug in the team member resource where changing the email in the configuration would result in no real changes. Changing the email will now force a replacement.

NOTES:

• The launchdarkly_feature_flag_environment resource's targeting_enabled argument has been deprecated in favor of on. Please update your config to use on in order to maintain compatibility with future versions.

• The resource_launchdarkly_access_token resource's policy_statements argument has been deprecated in favor of inline_roles. Please update your config to use inline_roles in order to maintain compatibility with future versions.