cloudscheduler: resume paused Job when paused is removed from config

[philip-harvey]

Fixes hashicorp/terraform-provider-google#29280

Summary

Fixes a bug where a Cloud Scheduler Job that was paused via paused = true would remain paused after the attribute was removed from configuration, even though the field docs state jobs default to enabled when unset.

Root cause

paused uses default_from_api: true, making the schema field Optional + Computed. When the attribute is removed from config, Terraform carries the prior state value (true) forward instead of treating it as unset. No diff is produced, so d.HasChange("paused") in the post_update handler is false and the :resume RPC never fires.

Fix

New resumeJobWhenPausedUnset CustomizeDiff: when the raw config value for paused is null but the current (state) value is true, force the new value to false. This restores the documented default and produces the diff that drives the existing resume logic. Setting paused = false explicitly is unchanged.

Tests

• Added TestAccCloudSchedulerJob_pausedRemovedResumes: sets paused = true (asserts PAUSED), then removes the attribute entirely (asserts paused = false / state = ENABLED). The pre-existing schedulerPausedExample test only flipped paused to an explicit false, so this regression was previously untested.

Verification

Generated the beta provider and ran locally:

• go build / go vet cloudscheduler service — clean
• Unit tests — pass
• Confirmed resumeJobWhenPausedUnset is emitted and registered in CustomizeDiff.All(...)

Acceptance test requires GCP credentials and is left to CI.

Release Note

cloudscheduler: fixed `google_cloud_scheduler_job` staying paused when the `paused` field is removed from configuration

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[github-actions]

Googlers: For automatic test runs see go/terraform-auto-test-runs.

@c2thorn, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

[philip-harvey]

@c2thorn are you able to take a look at this PR. Thanks

[github-actions]

@c2thorn This PR has been waiting for review for 3 weekdays. Please take a look! Use the label disable-review-reminders to disable these notifications.

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes for commit 1c48aec:

Diff report

Your PR generated the following diffs in downstream repositories:

Repository	Diff Link	Changes
google provider	View Diff	2 files changed, 78 insertions(+)
google-beta provider	View Diff	2 files changed, 78 insertions(+)
terraform-google-conversion	View Diff	1 file changed, 23 insertions(+)

Test report

Analytics

Total Tests	Passed	Skipped	Affected
9	8	0	1

Affected Service Packages

• cloudscheduler

Learn how VCR tests work

---

Step 1: Replaying Mode

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit.

Click here to see the affected tests

• TestAccCloudSchedulerJob_pausedRemovedResumes

View the replaying VCR build log

---

Step 2: Recording Mode

Recording Mode	Replaying Rerun	Test Name
✅ Log	✅	TestAccCloudSchedulerJob_pausedRemovedResumes

🟢 All tests passed!

View the recording VCR build log or the debug logs folder for detailed results.

@philip-harvey, @roaks3, @c2thorn VCR tests complete for 1c48aec!

[roaks3]

I was looking at the bug so just taking over the review here. Test basically confirms correct behavior (it's an additional test, but only takes ~15 sec to run), and implementation makes sense