chore(deps): update terraform launchdarkly to v2.20.2 #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.15.2
->2.20.2
Release Notes
launchdarkly/terraform-provider-launchdarkly (launchdarkly)
v2.20.2
Compare Source
Fixed:
launchdarkly_team
resource that prevented changes to thekey
from requiring the resource to be destroyed and recreated.v2.20.1
Compare Source
Fixed:
api_host
from being respected when using thelaunchdarkly_team_role_mapping
resource.launchdarkly_team_role_mapping
resource that prevented creating the resource with an emptycustom_role_keys
array.v2.20.0
Compare Source
Added:
launchdarkly_audit_log_subscription
resource and data source to support the Last9 integration.v2.19.0
Compare Source
Added:
dynatrace-cloud-automation
integration_key
on thelaunchdarkly_flag_trigger
resource.Updated:
v2.18.4
Compare Source
Fixed:
Updated:
v2.18.3
Compare Source
Added:
critical
field onlaunchdarkly_environment
.Changed:
v2.18.2
Compare Source
Improvements:
launchdarkly_feature_flag_environment
docs example to make it more clear that it's a feature flag environment, not an environment.v2.18.1
Compare Source
Fixed:
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.v2.18.0
Compare Source
Fixed:
launchdarkly_feature_flag_environment
was removed.Added:
launchdarkly_feature_flag
resource and data source with the newteam_maintainer_key
attribute field.Improvements:
v2.17.0
Compare Source
Added:
service_kind
andservice_config
attributes thelaunchdarkly_environment
's approval settings. With these settings you can configure the ServiceNow approval system. Thanks, @arhill05 #191v2.16.0
Compare Source
Added:
launchdarkly_segment
resource and data source. Thanks, @christogav! #187Improvements:
launchdarkly_segment
data source and resource using terraform-plugin-docs.Configuration
📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.