Inconsistent result error with recurring_schedule start field in Datadog_downtime_schedule creation

[Rams2408]

Datadog Terraform Provider Version

v3.46.0

Terraform Version

v1.5.7

What resources or data sources are affected?

datadog_downtime_schedule

Terraform Configuration Files

resource "datadog_downtime_schedule" "mq_broker_maintenance" {
count = var.enable ? 1 : 0
scope = "env:${var.environment}"

monitor_identifier {
monitor_id = datadog_monitor.heap_momory_usage_monitor[0].id
}

recurring_schedule {
recurrence {
duration = "2h" # Duration of the downtime (2 hours from 23:59 to 01:59 UTC)
rrule = "FREQ=WEEKLY;INTERVAL=1;BYDAY=SA" # Weekly recurrence on Saturdays
start = "2024-11-02T23:59" # Example date and time for the first occurrence of the downtime
}
timezone = "UTC" # Use UTC or adjust to your preferred timezone
}

display_timezone = "UTC"
message = "Scheduled weekly maintenance window for minor version upgrades on the MQ broker"
mute_first_recovery_notification = true
notify_end_states = ["alert", "warn"]
notify_end_types = ["canceled", "expired"]
}

Relevant debug or panic output

The following error appears when I run terraform apply:

Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.datadog_dashboards_and_monitors.module.heap_memory_usage_monitor.datadog_downtime_schedule.mq_broker_maintenance[0], provider
│ "provider["registry.terraform.io/datadog/datadog"]" produced an unexpected new value: .recurring_schedule.recurrence[0].start: was cty.StringVal("2024-11-02T23:59"),
│ but now cty.StringVal("2024-11-02T23:59:00").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Expected Behavior

The recurring downtime schedule should be created with the specified start time in the correct format, without resulting in an "inconsistent result" error.

Actual Behavior

When running terraform apply to create the datadog_downtime_schedule resource, I encounter an error indicating an "inconsistent result" due to a discrepancy in the start field.

Steps to Reproduce

terraform apply

Important Factoids

No response

References

#2535