From 46732b1de5c2d81a6e0eee7c11a44462cc278a86 Mon Sep 17 00:00:00 2001 From: A Vertex SDK engineer Date: Thu, 27 Aug 2026 10:45:21 -0700 Subject: [PATCH] feat: Expose service_attachment field on SandboxEnvironmentConnectionInfo across Python, Java, JS, and Go SDKs. The read-only serviceAttachment field is populated by the backend on sandboxes whose template enables private ingress (SandboxEnvironmentTemplate.ingress_control_config), and carries the PSC-E service attachment name customers need to create the consumer-side Private Service Connect endpoint in their VPC. PiperOrigin-RevId: 972038744 --- src/types/common.ts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/types/common.ts b/src/types/common.ts index 8a7f6792..f980a873 100644 --- a/src/types/common.ts +++ b/src/types/common.ts @@ -2329,6 +2329,8 @@ export declare interface SandboxEnvironmentConnectionInfo { sandboxInternalIp?: string; /** Output only. The routing token for the SandboxEnvironment. */ routingToken?: string; + /** Output only. The name of the PSC-E service attachment created for private ingress to this SandboxEnvironment. Only populated when the template enables private ingress (see SandboxEnvironmentTemplate.ingress_control_config). VPC-SC customers use this to create a PSC endpoint in their VPC. */ + serviceAttachment?: string; } /** A sandbox environment. */