Skip to content

Update WorkerPool.yaml to prevent persistent diff on the scaling_mode field#2

Closed
kminsu-google wants to merge 3 commits into
mainfrom
kminsu-google-manual-scaling-diff-issue
Closed

Update WorkerPool.yaml to prevent persistent diff on the scaling_mode field#2
kminsu-google wants to merge 3 commits into
mainfrom
kminsu-google-manual-scaling-diff-issue

Conversation

@kminsu-google
Copy link
Copy Markdown
Owner

@kminsu-google kminsu-google commented Jan 2, 2026

BUGFIX: cloudrunv2: fixed a perpetual diff on the `google_cloud_run_v2_worker_pool` resource where `scaling.scaling_mode` would show a change from `"MANUAL"` to `null` even when no changes were made to the configuration. Terraform now correctly recognizes the API's default of `"MANUAL"` for this field when the `scaling` block is present.

… field

The `google_cloud_run_v2_worker_pool` resource would show a perpetual diff
on the `scaling.scaling_mode` field. When the `scaling` block was
configured (e.g., with `manual_instance_count`) but `scaling_mode` was
omitted, Terraform would try to remove the `scaling_mode` attribute
on subsequent plans.

This occurred because the Cloud Run API defaults `scaling_mode` to "MANUAL"
if not specified, but the Terraform resource schema did not reflect this default.

This commit updates the `scaling.scaling_mode` field in the magic-modules
YAML definition to include `default_value: 'MANUAL'` and ensures it is
marked as `computed: true`. This aligns Terraform's behavior with the API,
resolving the persistent diff.
For magic module context this should be `optional` which later will be translated into `computed` in Terraform.
@kminsu-google
Copy link
Copy Markdown
Owner Author

Need further clarification. Will come back to this with fresh PR

@kminsu-google kminsu-google deleted the kminsu-google-manual-scaling-diff-issue branch January 2, 2026 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant