Issue Summary

When using the Atlassian Operations Terraform Provider to provision a atlassian-operations_schedule_rotation with a start_date that includes a timezone offset, the operation fails due to a date-time data type format mismatch between the Terraform provider and the JSM Ops API endpoints.

Steps to Reproduce

1. Follow the documentation to set up the Atlassian Operations Terraform Provider: Set up Atlassian Operations Terraform Provider.

1. Attempt to provision a atlassian-operations_schedule_rotation resource with a start_date value that includes a timezone offset, e.g., 2024-11-11T09:00:00+01:00.

1. Apply the Terraform configuration.

Expected Results

The atlassian-operations_schedule_rotation should be provisioned successfully with the specified start_date and timezone offset.

Actual Results

The operation fails, and the following error message is displayed:
 

Error: Provider produced inconsistent result after applyWhen applying changes to
atlassian-operations_schedule_rotation.these["Weekly rotation"], provider
"provider[\"registry.terraform.io/atlassian/atlassian-operations\"]"
produced an unexpected new value: .start_date: was
cty.StringVal("2024-11-11T09:00:00+01:00"), but now
cty.StringVal("2024-11-11T08:00:00Z").This is a bug in the provider, which should be reported in the provider's
own issue tracker.

Impact: This bug is blocking important operations, as users are unable to provision schedule rotations with timezone offsets.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available