Encapsulates client state, including executor, credentials, and transport channel.
Unlike ClientSettings which allows users to configure the client,
ClientContext is intended to be used in generated code. Most users will not need to use it.
The objects that need to be closed in order to clean up the resources created in the process of
creating this ClientContext. This will include the closeables from the transport context.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The `ClientContext` class encapsulates client state, including executor, credentials, and transport channel, primarily for internal use in generated code rather than direct user interaction."],["This page details the `ClientContext` for version 2.58.0, with links to documentation for many different versions, including the latest version which is currently 2.63.1."],["The `ClientContext` class provides static methods for creation like `create` with either `ClientSettings` or `StubSettings`, and `newBuilder` to create a new context with default values, both of which can throw an `IOException`."],["`ClientContext` contains methods to get various aspects of the context, including the clock, credentials, executor, headers, and a list of resources that need to be cleaned up."],["`ClientContext` also contains methods to retrieve various strings including the endpoint, API audience, quota project id, and the universe domain."]]],[]]
