google_cloud_scheduler_job attribute retry_config does not maintain state

[lc-chrisbarton]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

terraform -v
Terraform v0.12.24
+ provider.google v3.18.0

Affected Resource(s)

• google_cloud_scheduler_job attribute retry_config

Terraform Configuration Files

resource "google_cloud_scheduler_job" "job_run_svc_calculate_analytics_behaviors" {

  name             = "RUN_SVC_CALCULATE_ANALYTICS_BEHAVIORS"
  schedule         = "0 5 * * *"
  attempt_deadline = "900s"
  retry_config {
    retry_count = 1
  }
  http_target {
    http_method = "POST"
    uri         = "https://run.${var.env}.acme.com/run/v1/schedule-workloads?type=CALCULATE_ANALYTICS_BEHAVIORS&kubernetes_cluster=models&kubernetes_cluster_zone=us-central1-a"
    oidc_token {
      service_account_email = var.sa_cloud_scheduler_push_svc_email
      audience              = "run-svc"
    }
  }
}

Expected Behavior

After applying the change if we run terraform apply again we expect there are no changes to apply.

Actual Behavior

After applying the change if we run terraform apply again we get this output

-/+ resource "google_cloud_scheduler_job" "job_run_svc_calculate_analytics_behaviors" {
        attempt_deadline = "900s"
      ~ id               = "projects/acme/locations/us-central1/jobs/RUN_SVC_CALCULATE_ANALYTICS_BEHAVIORS" -> (known after apply)
        name             = "RUN_SVC_CALCULATE_ANALYTICS_BEHAVIORS"
      ~ project          = "acme" -> (known after apply)
      ~ region           = "us-central1" -> (known after apply)
        schedule         = "0 5 * * *"
        time_zone        = "Etc/UTC"

      ~ http_target {
          - headers     = {} -> null
            http_method = "POST"
            uri         = "https://run.prd.acme.com/run/v1/schedule-workloads?type=CALCULATE_ANALYTICS_BEHAVIORS&kubernetes_cluster=models&kubernetes_cluster_zone=us-central1-a"

            oidc_token {
                audience              = "run-svc"
                service_account_email = "id-cloud-scheduler-push-svc@acme.iam.gserviceaccount.com"
            }
        }

      ~ retry_config {
          - max_backoff_duration = "3600s" -> null # forces replacement
          - max_doublings        = 5 -> null # forces replacement
          - max_retry_duration   = "0s" -> null # forces replacement
          - min_backoff_duration = "5s" -> null # forces replacement
            retry_count          = 1
        }
    }

[edwardmedia]

@lc-chrisbarton yes I can repro this issue

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!