composer: stop logging user_workloads_secret data in debug logs

[naruto-lgtm]

Repro: apply a change to google_composer_user_workloads_secret.data with TF_LOG=DEBUG; the base64 secret values show up in the provider log.

Cause: the update path marshals the whole composer.UserWorkloadsSecret (including the data map, which the schema marks Sensitive: true) and logs it, and both create and update also log the marshaled API response. The SDK redacts data from plan/state, but log.Printf bypasses that redaction.

Fix: drop the marshaled bodies from those DEBUG lines and log only the resource id, so the secret material never reaches the logs.

Release Note Template for Downstream PRs (will be copied)

composer: fixed `google_composer_user_workloads_secret` writing the secret `data` values into provider debug logs

[github-actions]

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

@roaks3, 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.

[roaks3]

LGTM, thanks! Just waiting on checks

[modular-magician]

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

Diff report

Your PR generated the following diffs in downstream repositories:

Repository	Diff Link	Changes
google provider	View Diff	1 file changed, 7 insertions(+), 8 deletions(-)
google-beta provider	View Diff	1 file changed, 7 insertions(+), 8 deletions(-)

Test report

Analytics

Total Tests	Passed	Skipped	Affected
40	39	1	0

Affected Service Packages

• composer

Learn how VCR tests work

---

Step 1: Replaying Mode

🟢 All tests passed in Replaying mode! No Recording was needed.

View the replaying VCR build log

@naruto-lgtm VCR tests complete for f48b3bf!