- Added a note to global
launchdarkly_feature_flag
documentation about managing variations for env-level flag configurations outside of Terraform.
- Added support for managing the Kosli integration with the
launchdarkly_audit_log_subscription
resource and data source. - Add missing fields
analysis_type
,include_units_without_events
,percentile_value
, andunit_aggregation_type
to thelaunchdarkly_metric
resource and data provider. - Added the computed
version
attribute tolaunchdarkly_metric
.
- Deprecated the
launchdarkly_metric
'sis_active
attribute. This attribute is no longer used by LaunchDarkly and is safe to remove from Terraform configs.
- Fixed a bug in the
launchdarkly_team
resource that prevented changes to thekey
from requiring the resource to be destroyed and recreated. - Bump google.golang.org/grpc from 1.64.0 to 1.64.1 to address CVE-2023-45288.
- Fixed a bug that prevented
api_host
from being respected when using thelaunchdarkly_team_role_mapping
resource. - Fixed a bug in the
launchdarkly_team_role_mapping
resource that prevented creating the resource with an emptycustom_role_keys
array.
- Updated
launchdarkly_audit_log_subscription
resource and data source to support the Last9 integration.
- Added support for the
dynatrace-cloud-automation
integration_key
on thelaunchdarkly_flag_trigger
resource.
- Documentation for all resources and data sources is now generated from the underlying schema using tf-plugin-docs.
- Updated various dependencies.
- Do not retry 409s from LaunchDarkly.
- Update LaunchDarkly API client dependency to v16.
critical
field onlaunchdarkly_environment
.
- Updated examples to show use of all clause property
- Updated the resource name in our
launchdarkly_feature_flag_environment
docs example to make it more clear that it's a feature flag environment, not an environment. - Updated the LD API client from v14 to v15.
- Fixed the "Default off variation must be a valid index in the variations list" error for cases where the default variations were defined when creating a
launchdarkly_feature_flag
but no variations were explicitly defined (in the case of a default boolean flag, for example). - Adds a default value "HigherThanBaseline" to the
launchdarkly_metric.success_criteria
field to correspond to the same change in the API.
- Fixed a bug surfaced by issue #198 where feature flag configuration off variations were being reverted to an incorrect default value when a
launchdarkly_feature_flag_environment
was removed.
- Added previously missing support for team maintainers on the
launchdarkly_feature_flag
resource and data source with the newteam_maintainer_key
attribute field.
- Updated the LD API client to v0.14.
- Added the
service_kind
andservice_config
attributes thelaunchdarkly_environment
's approval settings. With these settings you can configure the ServiceNow approval system. Thanks, @arhill05 #191
- Added additional fields related to big segments to the
launchdarkly_segment
resource and data source. Thanks, @christogav! #187
- Generated documentation for the
launchdarkly_segment
data source and resource using terraform-plugin-docs.
- Added 404 retries to the
launchdarkly_team_role_mapping
resource. #179 - Fixed a bug related to how tags are updated in the
launchdarkly_environment
resource.
- Generate
launchdarkly_feature_flag
documentation from schema. - Fix typo in webhook example code. Thanks, @lachlancooper #180
- Adds the new optional
http_timeout
attribute to the provider config. This attribute allows you to configure the HTTP request timeout when the provider makes API calls to LaunchDarkly. #174
- Minor docs formatting errors.
- Adds the new optional
http_timeout
attribute to the provider config. This attribute allows you to configure the HTTP request timeout when the provider makes API calls to LaunchDarkly. #174 - Updates some of the public documentation using terraform-plugin-docs.
- Increased the
launchdarkly_project
key length validation from 20 characters to 100 characters. #175
- Fix YAML frontmatter on
launchdarkly_relay_proxy_configuration
documentation. Thanks, @felixlut #171
- Fixed a bug in the
launchdarkly_project
resource which prevented importing and managing a project with more than 20 environments. #154
- Improved the
launchdarkly_team_role_mapping
documentation to include a reference to the team sync with SCIM feature. #152
- Fixed an incorrect header in the
launchdarkly_team_role_mapping
resource documentation. #152
FEATURES:
- Adds the new
launchdarkly_team_role_mapping
resource to manage the custom roles associated with a LaunchDarkly team. This is useful if the LaunchDarkly team is created and managed externally, such as via Okta SCIM. If you wish to create an manage the team using Terraform, we recommend using thelaunchdarkly_team
resource instead. #152
BUG FIXES:
- Fixes an issue in the
launchdarkly_feature_flag_environment
resource where emptyfallthrough
blocks would cause the provider to panic. - Fixes the release pipeline
BUG FIXES:
- Fixes an issue in the
launchdarkly_feature_flag_environment
resource where emptyfallthrough
blocks would cause the provider to panic.
FEATURES:
-
Adds the optional
randomization_units
attribute to thelaunchdarkly_metric
resource and data source. For more information, read Allocating experiment audiences. Thanks, @goldfrapp04! -
Bumps golang.org/x/net dependency from 0.1.0 to 0.7.0.
-
Bumps Go version to 1.19.
NOTES:
- Fixes incorrect attribute casing in
launchdarkly_metric
resource and data source documentation.
FEATURES:
-
Adds a new
context_targets
attribute tolaunchdarkly_feature_flag_environment
resource blocks that allow you to target based on context kinds other than"user"
. -
Adds a new
context_kind
field tolaunchdarkly_feature_flag_environment
fallthrough blocks. -
Adds a new
context_kind
field tolaunchdarkly_feature_flag_environment
rule clauses. -
Adds
included_contexts
andexcluded_contexts
attribute tolaunchdarkly_segment
resource blocks that allow you to target based on context kinds other than"user"
. -
Adds a new
rollout_context_kind
field tolaunchdarkly_segment
rule blocks. -
Adds
user_identities
field to thelaunchdarkly_destination
mParticle configuration attribute that allow you to define mParticle user identities in tandem with their corresponding LaunchDarkly context kind.
FEATURES:
- Adds the optional
description
argument to the nestedrules
blocks on thelaunchdarkly_feature_flag_environment
resource and data source.
BUG FIXES:
- Fixes an issue on the
launchdarkly_feature_flag
resource affecting some customers where theclient_side_availability
property would sometimes unexpectedly update. Also updates the behavior of that field to not default back to project defaults even if removed, in keeping with the behavior of the LaunchDarkly API. If a feature flag resource is created for the first time withoutclient_side_availability
set, it will be set to the project defaults.
BUG FIXES:
-
Fixes a bug that allowed target blocks to be defined with no values in Terraform, resulting in a plan differential post-apply. A minimum of 1 item has been applied to the
values
field oflaunchdarkly_feature_flag_environment
resource blocks. -
Fixes a bug where removal of
tags
onresource_launchdarkly_segment
was not resulting in the actual deletion of tags.
NOTES:
- Adds a note to the
launchdarkly_feature_flag_environment
documentation to recommend against usage with experimentation. - Updates links to LaunchDarkly product and REST API documentation.
BUG FIXES:
- Adds
ignore_changes
guide to the documentation sidebar - Fixes broken link in
account_members
resource documentation
BUG FIXES:
- Correctly set bucketBy to nil when explicitly set to an empty string to avoid API errors #120
- Print error message from API response for
launchdarkly_team
resource
NOTES:
- Add
ignore_changes
guide
BUG FIXES:
- Fixes a bug in the
launchdarkly_feature_flag
resource where explicit defaults were not getting set for boolean flags upon creation.
BUG FIXES:
-
Fixes a bug in the
launchdarkly_feature_flag_environment
that prevented users from updating targeting rule clauses when the targeting rule was being used as the fallthrough variation with a percentage rollout. -
Fixes a bug in the
launchdarkly_feature_flag_environment
that resulted in the defaultstring
rule clause value type not being respected. #102
FEATURES:
- Add
no_access
role as a valid value for therole
key for thelaunchdarkly_team_member
resource.
FEATURES:
- Added
launchdarkly_team
data source and provider.
NOTES:
- Updated LaunchDarkly go api client from v7 to v10.
BUG FIXES:
- Remove invalid configurations from the
launchdarkly_audit_log_subscription
resource.
BUG FIXES:
- The
launchdarkly_feature_flag_environment
data source now checks whether the environment exists and prints out a more descriptive error. #101
NOTES:
- Upgrade Go version to 1.18
FEATURES:
- Added the
base_permissions
field to thelaunchdarkly_custom_role
resource.
NOTES:
- Removed callout to
bypassRequiredApproval
action in documentation pending further development. - Fix formatting in some documentation
ENHANCEMENTS:
- Added the
hide_member_details
argument to the Datadogconfig
for thelaunchdarkly_audit_log_subscription
resource. Whenhide_member_details
istrue
, LaunchDarkly member information will be redacted before events are sent to Datadog.
NOTES:
- Added a callout to the
bypassRequiredApproval
action in documentation.
FEATURES:
- Added Slack webhooks to the
launchdarkly_audit_log_subscription
resource and data source. #16 - Added more Datadog host URLs to the Datadog
launchdarkly_audit_log_subscription
resource.
BUG FIXES:
- Fixed an issue where the
config
was not being set on thelaunchdarkly_audit_log_subscription
data source.
BUG FIXES:
-
Fixed a bug preventing
launchdarkly_flag_trigger
s from being created in theenabled
state. -
Fixed a bug introduced in v2.2.0 where
launchdarkly_segments
withrule
blocks not containing aweight
were defaulting to aweight
of 0.
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.
FEATURES:
- Added
default_client_side_availability
block to thelaunchdarkly_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
andlaunchdarkly_environment
resources which caused Terraform to crash when environment approvals settings are omitted from the LaunchDarkly API response.
NOTES:
-
The
launchdarkly_project
resource's argumentinclude_in_snippet
has been deprecated in favor ofdefault_client_side_availability
. Please update your config to usedefault_client_side_availability
in order to maintain compatibility with future versions. -
The
launchdarkly_project
data source's attributeclient_side_availability
has been renamed todefault_client_side_availability
. Please update your config to usedefault_client_side_availability
in order to maintain compatibility with future versions.
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 thelaunchdarkly_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 argumentinclude_in_snippet
has been deprecated in favor ofclient_side_availability
. Please update your config to useclient_side_availability
in order to maintain compatibility with future versions.
ENHANCEMENTS:
- Upgraded the LaunchDarkly API client to version 7.
BUG FIXES:
-
Fixed an oversight in the approval settings where the environment
approval_settings
propertycan_apply_declined_changes
was defaulting tofalse
where it should have been defaulting totrue
in alignment with the LaunchDarkly API. -
Updated an error message.
FEATURES:
-
Added
approval_settings
blocks to thelaunchdarkly_environment
resource and nestedenvironments
blocks on thelaunchdarkly_project
resource. -
Added a boolean
archive
attribute on thelaunchdarkly_feature_flag
resource to allow archiving and unarchiving flags instead of deleting them.
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 thelaunchdarkly_project
resource. Please keep in mind if you have not added all of the existing environments to your Terraform config before importing alaunchdarkly_project
resource, Terraform will delete these environments from LaunchDarkly during the nextterraform apply
. If you wish to manage project properties with Terraform but not nested environments consider using Terraform's ignore changes lifecycle meta-argument.
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
andlaunchdarkly_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 oneenvironments
attribute will now beRequired
on thelaunchdarkly_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
resourceenabled
field has been removed in favor ofon
.on
now defaults tofalse
when not explicitly set. -
The
default_on_variation
anddefault_off_variation
properties on thelaunchdarkly_feature_flag
resource have now been replaced with a computeddefaults
block containing the propertieson_variation
andoff_variation
that refer to the variations in question by index rather than value. -
The
launchdarkly_feature_flag_environment
resource and data sourcetarget
attribute schema has been modified to include a newvariation
attribute. Herevariation
represents the index of the feature flag variation to serve if a user target is matched. -
The deprecated
launchdarkly_feature_flag_environment
resourcetargeting_enabled
field has been removed in favor ofon
.on
now defaults tofalse
when not explicitly set. -
The deprecated
launchdarkly_feature_flag_environment
resourceuser_targets
field has been removed in favor oftargets
.targets
now defaults to null when not explicitly set. -
The deprecated
launchdarkly_feature_flag_environment
resourceflag_fallthrough
field has been removed in favor offallthrough
. -
The deprecated
launchdarkly_webhooks
resourceenabled
field has been removed in favor ofon
.on
is now a required field. -
The deprecated
launchdarkly_webhooks
resourcepolicy_statements
field has been removed in favor ofstatements
. -
off_variation
andfallthrough
(previouslyflag_fallthrough
) onlaunchdarkly_feature_flag_environment
are nowRequired
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 thelaunchdarkly_destination
resource -
include_in_snippet
on thelaunchdarkly_project
resource -
on the
launchdarkly_environment
resource and inenvironment
blocks on thelaunchdarkly_project
resource:-
secure_mode
-
default_track_events
-
require_comments
-
confirm_changes
-
default_ttl
(reverts to0
)
-
-
on the
launchdarkly_feature_flag_environment
resource:-
on
(previouslytargeting_enabled
, reverts tofalse
) -
rules
-
targets
(previouslyuser_targets
) -
prerequisites
-
track_events
(reverts tofalse
)
-
-
BUG FIXES:
-
Fixed a bug in the
launchdarkly_webhook
resource wherestatements
removed from the configuration were not being deleted in LaunchDarkly. -
The
launchdarkly_feature_flag
resourcemaintainer_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 thelaunchdarkly_feature_flag
andlaunchdarkly_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 asclient_side_availability.0.using_environment_id
).
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
andlaunchdarkly_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 oneenvironments
attribute will now beRequired
on thelaunchdarkly_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
resourceenabled
field has been removed in favor ofon
.on
now defaults tofalse
when not explicitly set. -
The
default_on_variation
anddefault_off_variation
properties on thelaunchdarkly_feature_flag
resource have now been replaced with a computeddefaults
block containing the propertieson_variation
andoff_variation
that refer to the variations in question by index rather than value. -
The
launchdarkly_feature_flag_environment
resource and data sourcetarget
attribute schema has been modified to include a newvariation
attribute. Herevariation
represents the index of the feature flag variation to serve if a user target is matched. -
The deprecated
launchdarkly_feature_flag_environment
resourcetargeting_enabled
field has been removed in favor ofon
.on
now defaults tofalse
when not explicitly set. -
The deprecated
launchdarkly_feature_flag_environment
resourceuser_targets
field has been removed in favor oftargets
.targets
now defaults to null when not explicitly set. -
The deprecated
launchdarkly_feature_flag_environment
resourceflag_fallthrough
field has been removed in favor offallthrough
. -
The deprecated
launchdarkly_webhooks
resourceenabled
field has been removed in favor ofon
.on
is now a required field. -
The deprecated
launchdarkly_webhooks
resourcepolicy_statements
field has been removed in favor ofstatements
. -
off_variation
andfallthrough
(previouslyflag_fallthrough
) onlaunchdarkly_feature_flag_environment
are nowRequired
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 thelaunchdarkly_destination
resource -
include_in_snippet
on thelaunchdarkly_project
resource -
on the
launchdarkly_environment
resource and inenvironment
blocks on thelaunchdarkly_project
resource:-
secure_mode
-
default_track_events
-
require_comments
-
confirm_changes
-
default_ttl
(reverts to0
)
-
-
on the
launchdarkly_feature_flag_environment
resource:-
on
(previouslytargeting_enabled
, reverts tofalse
) -
rules
-
targets
(previouslyuser_targets
) -
prerequisites
-
track_events
(reverts tofalse
)
-
-
BUG FIXES:
-
Fixed a bug in the
launchdarkly_webhook
resource wherestatements
removed from the configuration were not being deleted in LaunchDarkly. -
The
launchdarkly_feature_flag
resourcemaintainer_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 thelaunchdarkly_feature_flag
andlaunchdarkly_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 asclient_side_availability.0.using_environment_id
).
BUG FIXES:
- Fixes a bug where attempts to create
launchdarkly_feature_flag
variations with an empty string value were throwing a panic.
NOTES:
-
The
launchdarkly_feature_flag_environment
resource and data source'sflag_fallthrough
argument has been deprecated in favor offallthrough
. Please update your config to usefallthrough
in order to maintain compatibility with future versions. -
The
launchdarkly_feature_flag_environment
resource and data source'suser_targets
argument has been deprecated in favor oftargets
. Please update your config to usetargets
in order to maintain compatibility with future versions.
FEATURES:
- Added the
creation_date
attribute to thelaunchdarkly_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 beRequired
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'stargeting_enabled
argument has been deprecated in favor ofon
. Please update your config to useon
in order to maintain compatibility with future versions. -
The
launchdarkly_access_token
resource'spolicy_statements
argument has been deprecated in favor ofinline_roles
. Please update your config to useinline_roles
in order to maintain compatibility with future versions.
FEATURES:
- Added support for an
azure-event-hubs
data sourcekind
on thelaunchdarkly_destination
resource.
ENHANCEMENTS:
-
Improved 429 retry handling.
-
Upgraded the Go version to 1.16.
-
Upgraded the LaunchDarkly API client to v5.1.0.
BUG FIXES:
-
Fixed a bug in the feature flag resource where multivariate (non-boolean) resource config with zero variations would create a boolean flag.
-
Fixed a bug in the feature flag resource where
default_on_variation
anddefault_off_variation
would still show up interraform plan
following their removal. -
Updated the destination
config
Elem
type toTypeString
and made theconfig
field required. Added improved validation to check fields for different destination kinds.
NOTES:
- The
launchdarkly_destination
resource'senabled
argument has been deprecated in favor ofon
. Please update your config to useon
in order to maintain compatibility with future versions. - The
launchdarkly_webhook
resource'spolicy_statements
argument has been deprecated in favor ofstatements
. Please update your config to usestatements
in order to maintain compatibility with future versions. - The
launchdarkly_webhook
data source'spolicy_statements
attribute has been deprecated in favor ofstatements
. Please update all references ofpolicy_statements
tostatements
in order to maintain compatibility with future versions. - The
launchdarkly_webhook
resource'senabled
argument has been deprecated in favor ofon
. Please update your config to useon
in order to maintain compatibility with future versions. - The
launchdarkly_webhook
data source'senabled
attribute has been deprecated in favor ofon
. Please update your all references ofenabled
toon
in order to maintain compatibility with future versions.
BUG FIXES:
- Fixed a bug preventing number and boolean values in targeting rules clauses from working. The new
value_type
attribute must be set in order to utilize number and boolean values. All values for a given targeting rule clause must be of the same type. #51
FEATURES:
-
Added a
launchdarkly_project
data source. -
Added a
launchdarkly_environment
data source. -
Added a
launchdarkly_feature_flag
data source. -
Added a
launchdarkly_feature_flag_environment
data source. -
Added a
launchdarkly_segment
data source. -
Added a
launchdarkly_webhook
data source.
ENHANCEMENTS:
- Upgraded the LaunchDarkly API version to 3.5.0.
BUG FIXES:
-
Resolved issues with the
launchdarkly_project
'senvironments
attribute. This attribute is no longer marked as deprecated and should be used when you wish to override the behavior of creatingTest
andProduction
environments during project creation. -
Fixed a bug where creating a
launchdarkly_feature_flag_environment
with anoff_variation
was not actually setting the off variation.
NOTES:
- The
launchdarkly_project
'senvironments
attribute is no longer marked ascomputed
. This means that if you havelaunchdarkly_project
resources without nestedenvironments
that were created before this version, you will see a diff denoting the removal of the computed environments from your state. It is safe to apply this change as no changes be made to your LaunchDarkly resources when applied.
FEATURES:
- Fixed a bug where omitted optional
launchdarkly_feature_flag_environment
parameters where making unwanted changes to the resource upon creation. #38
FEATURES:
- Added the
launchdarkly_access_token
resource.
FEATURES:
- Added the
launchdarkly_access_token
resource.
NOTES:
- Point
go.mod
to github.com/launchdarkly/terraform-provider-launchdarkly - Automatically set version header at build time
NOTES:
- Patch release to support Terraform 0.13
ENHANCEMENTS:
- Change data source names from data_source* to data_source_launchdarkly*
- Add pagination for pulling team members in accordance with the latest version of the LaunchDarkly API
BUG_FIXES:
- Fix bug with setting JSON arrays as variation values.
- Fix two-step create that required making an additional API update call to set all parameters.
BUG_FIXES:
- Improve handling of API rate limits. #26
FEATURES:
- Added
default_on_variation
anddefault_off_variation
tolaunchdarkly_feature_flag
. These optional attributes can be used to set the default targeting behavior for flags in newly created environments. #10 #18
BUG_FIXES:
- Improve handling of API rate limits.
FEATURES:
- Added
/examples
, a directory containing a variety of detailed usage examples.
BUG_FIXES:
- Fix non-empty plan after creating a
launchdarkly_team_member
with a custom role. - Handle missing user target variations in
launchdarkly_feature_flag_environment
#23
BUG_FIXES:
- Fix import bug in
launchdarkly_project
introduced in 1.2.0 #21
NOTES:
- The
environments
block inlaunchdarkly_project
has been deprecated in favor of thelaunchdarkly_environment
resource. Please update your existing configurations to maintain future compatibility.
FEATURES:
- Add new resource
launchdarkly_destination
. This resource is used to manage LaunchDarkly data export destinations. - Add
policy_statements
tolaunchdarkly_webhook
andlaunchdarkly_custom_role
#16.
BUG_FIXES:
- Fixed bug preventing large number variations from being saved in the state correctly. #14
- Fixed bug in import validation. #19
NOTES:
- The
policy
block inlaunchdarkly_custom_role
has been deprecated in favor ofpolicy_statements
. Please migrate your existing configurations to maintain future compatibility.
FEATURES:
- Add
bucket_by
argument tolaunchdarkly_feature_flag_environment
to enable custom attributes for percentage rollouts. - Add
require_comments
andconfirm_changes
arguments tolaunchdarkly_environment
.
ENHANCEMENTS:
- Update keys.go to make keys uppercase.
BUG FIXES:
- Fix pagination bug with
launchdarkly_team_member
data source. - Fix custom roles acceptance test race condition.
ENHANCEMENTS:
- Use randomized project keys in acceptance tests so they can be run in parallel.
BUG FIXES:
- Set the LaunchDarkly API version header to version
20191212
FEATURES:
- Add tags attribute to
launchdarkly_environment
resource. #5 - Add
maintainer_id
input validation.
ENHANCEMENTS:
- Improve
tags
input validation.
BUG FIXES:
- Allow flag
maintainer_id
to be unset. #6 - Fix typo in initialization error message. Thanks @jen20
- Flags created with invalid schema are deleted instead of left dangling.
NOTES:
- First release.