launchdarkly_feature_flag documentation about managing variations for env-level flag configurations outside of Terraform.launchdarkly_audit_log_subscription resource and data source.analysis_type, include_units_without_events, percentile_value, and unit_aggregation_type to the launchdarkly_metric resource and data provider.version attribute to launchdarkly_metric.launchdarkly_metric's is_active attribute. This attribute is no longer used by LaunchDarkly and is safe to remove from Terraform configs.launchdarkly_team resource that prevented changes to the key from requiring the resource to be destroyed and recreated.api_host from being respected when using the launchdarkly_team_role_mapping resource.launchdarkly_team_role_mapping resource that prevented creating the resource with an empty custom_role_keys array.launchdarkly_audit_log_subscription resource and data source to support the Last9 integration.dynatrace-cloud-automation integration_key on the launchdarkly_flag_trigger resource.critical field on launchdarkly_environment.launchdarkly_feature_flag_environment docs example to make it more clear that it's a feature flag environment, not an environment.launchdarkly_feature_flag but no variations were explicitly defined (in the case of a default boolean flag, for example).launchdarkly_metric.success_criteria field to correspond to the same change in the API.launchdarkly_feature_flag_environment was removed.launchdarkly_feature_flag resource and data source with the new team_maintainer_key attribute field.service_kind and service_config attributes the launchdarkly_environment's approval settings. With these settings you can configure the ServiceNow approval system. Thanks, @arhill05 #191launchdarkly_segment resource and data source. Thanks, @christogav! #187launchdarkly_segment data source and resource using terraform-plugin-docs.launchdarkly_team_role_mapping resource. #179launchdarkly_environment resource.launchdarkly_feature_flag documentation from schema.