[Bug]: end_hour param on schedule for mongodbatlas_online_archive resource not working

[chalkboardbrad]

Is there an existing issue for this?

• I have searched the existing issues

Provider Version

v2.3.0

Terraform Version

v1.7.0

Terraform Edition

Terraform Open Source (OSS)

Current Behavior

latest docs seem to support the ability to set an end_hour parameter within the schedule block of the resource, a failure occurs during apply:

error creating MongoDB Atlas Online Archive:: https://cloud.mongodb.com/api/atlas/v2/groups/<REDACTED>/clusters/chalkboard/onlineArchives POST: HTTP 400 Bad Request (Error code: "INVALID_ATTRIBUTE") Detail: Invalid attribute endHour specified. Reason: Bad Request. Params: [endHour], BadRequestDetail:

removing end_hour from the schedule block returns successful apply and I can see the archive is created on the cluster.

Terraform configuration to reproduce the issue

+ resource "mongodbatlas_online_archive" "archive" {
      + archive_id      = (known after apply)
      + cluster_name    = "<REDACTED>"
      + coll_name       = "<REDACTED>"
      + collection_type = (known after apply)
      + db_name         = "<REDACTED>"
      + id              = (known after apply)
      + paused          = false
      + project_id      = "<REDACTED>"
      + state           = (known after apply)
      + sync_creation   = false

      + criteria {
          + date_field        = "createdAt"
          + date_format       = "ISODATE"
          + expire_after_days = 60
          + type              = "DATE"
        }

      + data_expiration_rule {
          + expire_after_days = 90
        }

      + partition_fields {
          + field_name = "createdAt"
          + field_type = (known after apply)
          + order      = 0
        }

      + schedule {
          + end_hour     = 9
          + end_minute   = 0
          + start_hour   = 8
          + start_minute = 0
          + type         = "DAILY"
        }
    }

Steps To Reproduce

1. attempt apply w the terraform provided above, observe error
2. remove end_hour parameter from schedule block
3. re-attempt apply, observe success

Additional comments:
It appears like the tf resource is accepting end_hour because I can see the provider is transforming it into an attribute named endHour, and that the error is happening between the provider and the mongo atlas API.

Logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thanks for opening this issue! Please make sure you've followed our guidelines when opening the issue. In short, to help us reproduce the issue we need:

• Terraform configuration file used to reproduce the issue
• Terraform log files from the run where the issue occurred
• Terraform Atlas provider version used to reproduce the issue
• Terraform version used to reproduce the issue
• Confirmation if Terraform OSS, Terraform Cloud, or Terraform Enterprise deployment

The ticket CLOUDP-369815 was created for internal tracking.

[chalkboardbrad]

for additional context, my goal was to set up a schedule where the daily archiving "job" could run any time between 8 and 9AM UTC

[chalkboardbrad]

Update: I have now realized that there is a minimum of a 2 hour window in the schedule. I would recommend the following improvements:

1. update example usage docs to use a valid schedule
2. update the API response BadRequestDetail to explain that the issue is due to the failed validation.

Regardless, I am unblocked.

[maastha]

Thank you @chalkboardbrad for creating this issue & sharing your findings!
You're right, I will update the example in the documentation & will check with the backend API team to improve the error message.

Thanks again for the feedback!

[chalkboardbrad]

You're most welcome! Have a great new year.

[maastha]

Hi @chalkboardbrad

I actually tried out the example we have and it seems to work fine, however, when I used your example values I received the same error. I'm checking with the backend team to understand the expected values before updating the example.

[chalkboardbrad]

maybe same values for start/end just means the entire day is a valid window?

[github-actions]

This issue has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

[maastha]

@chalkboardbrad I couldn't find any public documentation to confirm this, but I've reached out to the feature team to get more context on this. I will update once we hear back.
Hope this helps!

[github-actions]

This issue has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!