chore: Enhances User-Agent with additional metadata support #3463
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces enhanced user agent context propagation and analytics metadata for all resource, data source, and function operations. The changes include:
UserAgentExtratointernal/config/transport.gostruct and related helpers to capture operation type, name, and action for every provider call.WrappedProviderServerininternal/provider/wrapper_provider_server.go. A new file that wraps the provider server to inject detailed operation metadata into the context for every gRPC entrypoint. This wrapper ensures that all resource, data source, and function operations are enriched with type, name, and operation metadata, enabling improved observability, analytics, and debugging. The wrapper works by intercepting each call and usingAddUserAgentExtra.UserAgentTransportHTTP middleware that reads theUserAgentExtraand updates the request header.These changes improve observability, analytics, and debugging capabilities by making operation context available for logging and downstream systems.
Link to any related issue(s): CLOUDP-329015
Sequence diagram
sequenceDiagram autonumber participant Terraform as Terraform CLI/Cloud participant Wrapped as WrappedProviderServer participant Old as OldProviderServer participant Logic as Resource/Data Logic participant HTTP as HTTP RoundTripper/API Terraform->>Wrapped: gRPC Request (e.g., ReadResource) Wrapped->>Wrapped: AddUserAgentExtra(ctx, type, name, operation) Wrapped->>Old: Call OldProviderServer.ReadResource(ctx, req) Old->>Logic: Resource/Data Logic (uses ctx) Logic->>HTTP: HTTP Request with context HTTP->>HTTP: UserAgentTransport:<br/>Read UserAgentExtra from ctx<br/>Modify User-Agent header HTTP->>HTTP: TerraformLoggingTransport:<br/>Log request with final User-Agent HTTP->>HTTP: DigestTransport:<br/>Prepare for digest auth HTTP->>HTTP: Rest of the chain HTTP-->>Logic: API Response Logic-->>Old: Resource/Data Response Old-->>Wrapped: Response Wrapped-->>Terraform: ResponseAny logic, logging, or HTTP requests made further down the stack (including SDK calls) can now read this metadata from the context.
Type of change:
Required Checklist: