You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resource"datadog_monitor""monitor" {
enable_logs_sample=truemessage=<<EOF{{#is_alert}}**REDACTED**{{/is_alert}} EOFname="**READACTED**"query="logs(\"**READACTED**\").index(\"*\").rollup(\"count\").last(\"1455m\") < 1"renotify_interval=(60*24) +30# 1 day and 30 minutestags=["team:**READACTED**"]
type="log alert"monitor_thresholds {
critical=1
}
}
resource"datadog_downtime_schedule""schedule" {
scope="*"display_timezone="Europe/London"message="No notifications are expected to be sent over the weekend"monitor_identifier {
monitor_id=datadog_monitor.monitor.id
}
recurring_schedule {
recurrence {
# All day Sat + All day Sun + Monday morning until 10:35amduration="${tostring(((24+24+10) *60) +35)}m"rrule="FREQ=WEEKLY;INTERVAL=1"# When creating the resource the start date must be in the future, but for updates can be in the paststart="2024-04-06T00:00:00"
}
timezone="Europe/London"
}
}
Relevant debug or panic output
│ Error: Value Conversion Error
│
│ with module.staging_alerts.datadog_downtime_schedule.notify_function_triggered_downtime,
│ on ../modules/alerts/notify_function_triggered_alerts.tf line 28, in resource "datadog_downtime_schedule" "schedule":
│ 28: monitor_identifier {
│
│ An unexpected error was encountered while verifying an attribute value
│ matched its expected type to prevent unexpected behavior or panics. This is
│ always an error in the provider. Please report the following to the
│ provider developer:
│
│ Expected framework type from provider logic:
│ types.SetType[basetypes.StringType] / underlying type:
│ tftypes.Set[tftypes.String]
│ Received framework type from provider logic: types.SetType[!!! MISSING TYPE
│ !!!] / underlying type: tftypes.Set[tftypes.DynamicPseudoType]
│ Path: monitor_identifier.monitor_tags
Expected Behavior
Should have applied the downtime to the monitor based on the id, should not require the tags
Actual Behavior
Failed to apply terraform
Steps to Reproduce
terraform apply
Important Factoids
I don't think many people are using this resource so likely is just broken
References
No response
The text was updated successfully, but these errors were encountered:
Datadog Terraform Provider Version
3.29.0
Terraform Version
1.5.7
What resources or data sources are affected?
resource_datadog_downtime_schedule
Terraform Configuration Files
Relevant debug or panic output
│ Error: Value Conversion Error
│
│ with module.staging_alerts.datadog_downtime_schedule.notify_function_triggered_downtime,
│ on ../modules/alerts/notify_function_triggered_alerts.tf line 28, in resource "datadog_downtime_schedule" "schedule":
│ 28: monitor_identifier {
│
│ An unexpected error was encountered while verifying an attribute value
│ matched its expected type to prevent unexpected behavior or panics. This is
│ always an error in the provider. Please report the following to the
│ provider developer:
│
│ Expected framework type from provider logic:
│ types.SetType[basetypes.StringType] / underlying type:
│ tftypes.Set[tftypes.String]
│ Received framework type from provider logic: types.SetType[!!! MISSING TYPE
│ !!!] / underlying type: tftypes.Set[tftypes.DynamicPseudoType]
│ Path: monitor_identifier.monitor_tags
Expected Behavior
Should have applied the downtime to the monitor based on the id, should not require the tags
Actual Behavior
Failed to apply terraform
Steps to Reproduce
terraform apply
Important Factoids
I don't think many people are using this resource so likely is just broken
References
No response
The text was updated successfully, but these errors were encountered: