initial write-only breaking change

[BBBmau]

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

simplify write-only (WIP changelog)

[modular-magician]

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

Diff report

Your PR generated the following diffs in downstream repositories:

Repository	Diff Link	Changes
google provider	View Diff	9 files changed, 67 insertions(+), 74 deletions(-)
google-beta provider	View Diff	9 files changed, 67 insertions(+), 74 deletions(-)
terraform-google-conversion	View Diff	8 files changed, 10 insertions(+), 121 deletions(-)

Breaking Change(s) Detected

The following breaking change(s) were detected within your pull request.

• Field http_check.auth_info.password_wo within resource google_monitoring_uptime_check_config was added to exactly one of - reference
• Field http_check.auth_info.password within resource google_monitoring_uptime_check_config was added to exactly one of - reference
• Field secret_data_wo_version changed from TypeInt to TypeString on google_secret_manager_secret_version - reference
• Field secret_data_wo_version default value changed from 0 to <nil> on google_secret_manager_secret_version - reference
• Field sensitive_params.secret_access_key_wo_version changed from TypeInt to TypeString on google_bigquery_data_transfer_config - reference
• Field sensitive_params.secret_access_key_wo within resource google_bigquery_data_transfer_config was added to exactly one of - reference
• Field sensitive_params.secret_access_key within resource google_bigquery_data_transfer_config was added to exactly one of - reference

If you believe this detection to be incorrect please raise the concern with your reviewer.
If you intend to make this change you will need to wait for a major release window.
An override-breaking-change label can be added to allow merging.

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_bigquery_data_transfer_config (12 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_bigquery_data_transfer_config" "primary" {
  sensitive_params {
    secret_access_key            = # value needed
    secret_access_key_wo         = # value needed
    secret_access_key_wo_version = # value needed
  }
}

Test report

Analytics

Total Tests	Passed	Skipped	Affected
107	96	8	3

Affected Service Packages

• bigquerydatatransfer
• monitoring
• secretmanager

Learn how VCR tests work

---

Step 1: Replaying Mode

Action taken

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

Click here to see the affected tests

• TestAccDatasourceSecretManagerSecretVersion_basic
• TestAccMonitoringUptimeCheckConfig_update_wo
• TestAccMonitoringUptimeCheckConfig_uptimeCheckConfigHttpPasswordWoExample

View the replaying VCR build log

---

Step 2: Recording Mode

Recording Mode	Replaying Rerun	Test Name
✅ Log	✅	TestAccDatasourceSecretManagerSecretVersion_basic
✅ Log	✅	TestAccMonitoringUptimeCheckConfig_update_wo
✅ Log	✅	TestAccMonitoringUptimeCheckConfig_uptimeCheckConfigHttpPasswordWoExample

🟢 All tests passed!

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

@BBBmau, @sachinpro VCR tests complete for 16bea9c!

[modular-magician]

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

Diff report

Your PR generated the following diffs in downstream repositories:

Repository	Diff Link	Changes
google provider	View Diff	10 files changed, 75 insertions(+), 82 deletions(-)
google-beta provider	View Diff	10 files changed, 75 insertions(+), 82 deletions(-)
terraform-google-conversion	View Diff	8 files changed, 10 insertions(+), 121 deletions(-)

Breaking Change(s) Detected

The following breaking change(s) were detected within your pull request.

• Field http_check.auth_info.password_wo within resource google_monitoring_uptime_check_config was added to exactly one of - reference
• Field http_check.auth_info.password within resource google_monitoring_uptime_check_config was added to exactly one of - reference
• Field secret_data_wo_version changed from TypeInt to TypeString on google_secret_manager_secret_version - reference
• Field secret_data_wo_version default value changed from 0 to <nil> on google_secret_manager_secret_version - reference
• Field sensitive_params.secret_access_key_wo_version changed from TypeInt to TypeString on google_bigquery_data_transfer_config - reference
• Field sensitive_params.secret_access_key_wo within resource google_bigquery_data_transfer_config was added to exactly one of - reference
• Field sensitive_params.secret_access_key within resource google_bigquery_data_transfer_config was added to exactly one of - reference
• Field template.spec.containers.liveness_probe.grpc within resource google_cloud_run_service was added to exactly one of - reference
• Field template.spec.containers.liveness_probe.http_get within resource google_cloud_run_service was added to exactly one of - reference
• Field template.spec.containers.readiness_probe.grpc within resource google_cloud_run_service was added to exactly one of - reference
• Field template.spec.containers.readiness_probe.http_get within resource google_cloud_run_service was added to exactly one of - reference
• Field template.spec.containers.startup_probe.grpc within resource google_cloud_run_service was added to exactly one of - reference
• Field template.spec.containers.startup_probe.http_get within resource google_cloud_run_service was added to exactly one of - reference
• Field template.spec.containers.startup_probe.tcp_socket within resource google_cloud_run_service was added to exactly one of - reference

If you believe this detection to be incorrect please raise the concern with your reviewer.
If you intend to make this change you will need to wait for a major release window.
An override-breaking-change label can be added to allow merging.

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_bigquery_data_transfer_config (12 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_bigquery_data_transfer_config" "primary" {
  sensitive_params {
    secret_access_key            = # value needed
    secret_access_key_wo         = # value needed
    secret_access_key_wo_version = # value needed
  }
}

Test report

Analytics

Total Tests	Passed	Skipped	Affected
146	0	16	130

Affected Service Packages

• monitoring
• secretmanager
• bigquerydatatransfer
• cloudrun

Learn how VCR tests work

---

Step 1: Replaying Mode

Action taken

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

More than 100 tests failed in replaying; this is too many to display on GitHub. View the Cloud Build logs to see the full list.

View the replaying VCR build log

---

Step 2: Recording Mode

More than 100 tests ran in recording mode; this is too many to display on GitHub. View the Cloud Build logs to see the result summary.

Caution

Issues requiring attention before PR completion

🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details.

Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer.

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

@BBBmau, @sachinpro VCR tests complete for 1d8fb27!