Jan Novak ed59a4c384 Surface GCP SDK HTTP wire logs at V(5) ...

Inject an option.WithLogger slog logger bridged to the zap sink via
logr.ToSlogHandler with a V(1) shift, so the SDK's Debug-level
"api request"/"api response" records (URL, headers, full payloads)
appear only at --zap-log-level=5. Startup warning when active, since
raw insert payloads include cloud-init user-data. Note WithLogger
overrides GOOGLE_SDK_GO_LOGGING_LEVEL for this client.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-08-11 18:39:37 +02:00

..

errors_test.go

Add the GCP provider: four-call surface, fire-and-forget ops, zone-qualified IDs

2026-08-09 15:36:14 +02:00

errors.go

Add V(1)/V(2) verbose logging to the GCP provider

2026-08-11 17:48:34 +02:00

gcp_test.go

Surface GCP SDK HTTP wire logs at V(5)

2026-08-11 18:39:37 +02:00

gcp.go

Surface GCP SDK HTTP wire logs at V(5)

2026-08-11 18:39:37 +02:00

insert_test.go

Add the GCP provider: four-call surface, fire-and-forget ops, zone-qualified IDs

2026-08-09 15:36:14 +02:00

insert.go

Add the GCP provider: four-call surface, fire-and-forget ops, zone-qualified IDs

2026-08-09 15:36:14 +02:00