Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

google_cloud_scheduler_job destroyed and recreated instead of update #8159

Labels

Comments

@maroux
Copy link
Contributor

maroux commented Jan 9, 2021

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

→ tf version
Terraform v0.13.5
+ provider registry.terraform.io/hashicorp/google v3.51.0
+ provider registry.terraform.io/hashicorp/google-beta v3.51.0

Affected Resource(s)

  • google_cloud_scheduler_job

Terraform Configuration Files

resource "google_pubsub_topic" "topic" {
  name = "job-topic"
}

resource "google_cloud_scheduler_job" "job" {
  name        = "test-job"
  description = "test job"
  schedule    = "*/2 * * * *"

  pubsub_target {
    topic_name = google_pubsub_topic.topic.id
    data       = base64encode("test")
  }
}

All fields other than the following can be updated using the REST API:

  • name
  • project
  • region

Expected Behavior

  • Changing fields like description, data should be update-able.

Actual Behavior

  • Changing description destroys and re-creates the job.

Steps to Reproduce

  1. Create job using supplied config: terraform apply
  2. Update description to test job2
  3. Run terraform plan
  4. Plan shows:
    ...
    resource "google_cloud_scheduler_job" "job" {
      ~ description = "test job" -> "test job2" # forces replacement
    ...
    

References

@ghost ghost added bug labels Jan 9, 2021
@venkykuberan venkykuberan self-assigned this Jan 11, 2021
@venkykuberan
Copy link
Contributor

@maroux API may have added the updated support after we worked on this resource. I will make this issue as a feature request.

@ghost
Copy link

ghost commented Feb 19, 2021

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 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Feb 19, 2021
@github-actions github-actions bot added forward/review In review; remove label to forward service/cloudscheduler labels Jan 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.