WorkspaceClient (databricks-sdk-java 0.24.0 API)

java.lang.Object
- com.databricks.sdk.WorkspaceClient

@Generated
public class WorkspaceClient
extends Object

Entry point for accessing Databricks workspace-level APIs

Constructor Summary

Constructors
Constructor and Description
`WorkspaceClient()`
`WorkspaceClient(boolean mock)` Constructor for mocks
`WorkspaceClient(boolean mock, ApiClient apiClient)` Constructor for mocks
`WorkspaceClient(DatabricksConfig config)`

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`AccountAccessControlProxyAPI`	`accountAccessControlProxy()` These APIs manage access rules on resources in an account.
`AlertsAPI`	`alerts()` The alerts API can be used to perform CRUD operations on alerts.
`ApiClient`	`apiClient()`
`AppsAPI`	`apps()` Lakehouse Apps run directly on a customer’s Databricks instance, integrate with their data, use and extend Databricks services, and enable users to interact through single sign-on.
`ArtifactAllowlistsAPI`	`artifactAllowlists()` In Databricks Runtime 13.3 and above, you can add libraries and init scripts to the `allowlist` in UC so that users can leverage these artifacts on compute configured with shared access mode.
`CatalogsAPI`	`catalogs()` A catalog is the first layer of Unity Catalog’s three-level namespace.
`CleanRoomsAPI`	`cleanRooms()` A clean room is a secure, privacy-protecting environment where two or more parties can share sensitive enterprise data, including customer data, for measurements, insights, activation and other use cases.
`ClusterPoliciesAPI`	`clusterPolicies()` You can use cluster policies to control users' ability to configure clusters based on a set of rules.
`ClustersExt`	`clusters()` The Clusters API allows you to create, start, edit, list, terminate, and delete clusters.
`CommandExecutionAPI`	`commandExecution()` This API allows execution of Python, Scala, SQL, or R commands on running Databricks Clusters.
`DatabricksConfig`	`config()`
`ConnectionsAPI`	`connections()` Connections allow for creating a connection to an external data source.
`ConsumerFulfillmentsAPI`	`consumerFulfillments()` Fulfillments are entities that allow consumers to preview installations.
`ConsumerInstallationsAPI`	`consumerInstallations()` Installations are entities that allow consumers to interact with Databricks Marketplace listings.
`ConsumerListingsAPI`	`consumerListings()` Listings are the core entities in the Marketplace.
`ConsumerPersonalizationRequestsAPI`	`consumerPersonalizationRequests()` Personalization Requests allow customers to interact with the individualized Marketplace listing flow.
`ConsumerProvidersAPI`	`consumerProviders()` Providers are the entities that publish listings to the Marketplace.
`CredentialsManagerAPI`	`credentialsManager()` Credentials manager interacts with with Identity Providers to to perform token exchanges using stored credentials and refresh tokens.
`CurrentUserAPI`	`currentUser()` This API allows retrieving information about currently authenticated user or service principal.
`DashboardsAPI`	`dashboards()` In general, there is little need to modify dashboards using the API.
`DashboardWidgetsAPI`	`dashboardWidgets()` This is an evolving API that facilitates the addition and removal of widgets from existing dashboards within the Databricks Workspace.
`DataSourcesAPI`	`dataSources()` This API is provided to assist you in making new query objects.
`DbfsExt`	`dbfs()` DBFS API makes it simple to interact with various data sources without having to include a users credentials every time to read a file.
`DbsqlPermissionsAPI`	`dbsqlPermissions()` The SQL Permissions API is similar to the endpoints of the :method:permissions/set.
`ExperimentsAPI`	`experiments()` Experiments are the primary unit of organization in MLflow; all MLflow runs belong to an experiment.
`ExternalLocationsAPI`	`externalLocations()` An external location is an object that combines a cloud storage path with a storage credential that authorizes access to the cloud storage path.
`FilesAPI`	`files()` The Files API is a standard HTTP API that allows you to read, write, list, and delete files and directories by referring to their URI.
`FunctionsAPI`	`functions()` Functions implement User-Defined Functions (UDFs) in Unity Catalog.
`GitCredentialsAPI`	`gitCredentials()` Registers personal access token for Databricks to do operations on behalf of the user.
`GlobalInitScriptsAPI`	`globalInitScripts()` The Global Init Scripts API enables Workspace administrators to configure global initialization scripts for their workspace.
`GrantsAPI`	`grants()` In Unity Catalog, data is secure by default.
`GroupsAPI`	`groups()` Groups simplify identity management, making it easier to assign access to Databricks workspace, data, and other securable objects.
`InstancePoolsAPI`	`instancePools()` Instance Pools API are used to create, edit, delete and list instance pools by using ready-to-use cloud instances which reduces a cluster start and auto-scaling times.
`InstanceProfilesAPI`	`instanceProfiles()` The Instance Profiles API allows admins to add, list, and remove instance profiles that users can launch clusters with.
`IpAccessListsAPI`	`ipAccessLists()` IP Access List enables admins to configure IP access lists.
`JobsAPI`	`jobs()` The Jobs API allows you to create, edit, and delete jobs.
`LakehouseMonitorsAPI`	`lakehouseMonitors()` A monitor computes and monitors data or model quality metrics for a table over time.
`LakeviewAPI`	`lakeview()` These APIs provide specific management operations for Lakeview dashboards.
`LibrariesAPI`	`libraries()` The Libraries API allows you to install and uninstall libraries and get the status of libraries on a cluster.
`MetastoresAPI`	`metastores()` A metastore is the top-level container of objects in Unity Catalog.
`ModelRegistryAPI`	`modelRegistry()` Note: This API reference documents APIs for the Workspace Model Registry.
`ModelVersionsAPI`	`modelVersions()` Databricks provides a hosted version of MLflow Model Registry in Unity Catalog.
`OnlineTablesAPI`	`onlineTables()` Online tables provide lower latency and higher QPS access to data from Delta tables.
`PermissionMigrationAPI`	`permissionMigration()` This spec contains undocumented permission migration APIs used in https://github.com/databrickslabs/ucx.
`PermissionsAPI`	`permissions()` Permissions API are used to create read, write, edit, update and manage access for various users on different objects and endpoints.
`PipelinesAPI`	`pipelines()` The Delta Live Tables API allows you to create, edit, delete, start, and view details about pipelines.
`PolicyFamiliesAPI`	`policyFamilies()` View available policy families.
`ProviderExchangeFiltersAPI`	`providerExchangeFilters()` Marketplace exchanges filters curate which groups can access an exchange.
`ProviderExchangesAPI`	`providerExchanges()` Marketplace exchanges allow providers to share their listings with a curated set of customers.
`ProviderFilesAPI`	`providerFiles()` Marketplace offers a set of file APIs for various purposes such as preview notebooks and provider icons.
`ProviderListingsAPI`	`providerListings()` Listings are the core entities in the Marketplace.
`ProviderPersonalizationRequestsAPI`	`providerPersonalizationRequests()` Personalization requests are an alternate to instantly available listings.
`ProviderProviderAnalyticsDashboardsAPI`	`providerProviderAnalyticsDashboards()` Manage templated analytics solution for providers.
`ProviderProvidersAPI`	`providerProviders()` Providers are entities that manage assets in Marketplace.
`ProvidersAPI`	`providers()` A data provider is an object representing the organization in the real world who shares the data.
`QueriesAPI`	`queries()` These endpoints are used for CRUD operations on query definitions.
`QueryHistoryAPI`	`queryHistory()` Access the history of queries through SQL warehouses.
`QueryVisualizationsAPI`	`queryVisualizations()` This is an evolving API that facilitates the addition and removal of vizualisations from existing queries within the Databricks Workspace.
`RecipientActivationAPI`	`recipientActivation()` The Recipient Activation API is only applicable in the open sharing model where the recipient object has the authentication type of `TOKEN`.
`RecipientsAPI`	`recipients()` A recipient is an object you create using :method:recipients/create to represent an organization which you want to allow access shares.
`RegisteredModelsAPI`	`registeredModels()` Databricks provides a hosted version of MLflow Model Registry in Unity Catalog.
`ReposAPI`	`repos()` The Repos API allows users to manage their git repos.
`SchemasAPI`	`schemas()` A schema (also called a database) is the second layer of Unity Catalog’s three-level namespace.
`SecretsExt`	`secrets()` The Secrets API allows you to manage secrets, secret scopes, and access permissions.
`ServicePrincipalsAPI`	`servicePrincipals()` Identities for use with jobs, automated tools, and systems such as scripts, apps, and CI/CD platforms.
`ServingEndpointsAPI`	`servingEndpoints()` The Serving Endpoints API allows you to create, update, and delete model serving endpoints.
`SettingsAPI`	`settings()` Workspace Settings API allows users to manage settings at the workspace level.
`SharesAPI`	`shares()` A share is a container instantiated with :method:shares/create.
`StatementExecutionAPI`	`statementExecution()` The Databricks SQL Statement Execution API can be used to execute SQL statements on a SQL warehouse and fetch the result.
`StorageCredentialsAPI`	`storageCredentials()` A storage credential represents an authentication and authorization mechanism for accessing data stored on your cloud tenant.
`SystemSchemasAPI`	`systemSchemas()` A system schema is a schema that lives within the system catalog.
`TableConstraintsAPI`	`tableConstraints()` Primary key and foreign key constraints encode relationships between fields in tables.
`TablesAPI`	`tables()` A table resides in the third layer of Unity Catalog’s three-level namespace.
`TokenManagementAPI`	`tokenManagement()` Enables administrators to get all tokens and delete tokens for other users.
`TokensAPI`	`tokens()` The Token API allows you to create, list, and revoke tokens that can be used to authenticate and access Databricks REST APIs.
`UsersAPI`	`users()` User identities recognized by Databricks and represented by email addresses.
`VectorSearchEndpointsAPI`	`vectorSearchEndpoints()` Endpoint**: Represents the compute resources to host vector search indexes.
`VectorSearchIndexesAPI`	`vectorSearchIndexes()` Index: An efficient representation of your embedding vectors that supports real-time and efficient approximate nearest neighbor (ANN) search queries.
`VolumesAPI`	`volumes()` Volumes are a Unity Catalog (UC) capability for accessing, storing, governing, organizing and processing files.
`WarehousesAPI`	`warehouses()` A SQL warehouse is a compute resource that lets you run SQL commands on data objects within Databricks SQL.
`WorkspaceClient`	`withAccountAccessControlProxyAPI(AccountAccessControlProxyAPI accountAccessControlProxy)` Replace the default AccountAccessControlProxyAPI with a custom implementation.
`WorkspaceClient`	`withAccountAccessControlProxyImpl(AccountAccessControlProxyService accountAccessControlProxy)` Replace the default AccountAccessControlProxyService with a custom implementation.
`WorkspaceClient`	`withAlertsAPI(AlertsAPI alerts)` Replace the default AlertsAPI with a custom implementation.
`WorkspaceClient`	`withAlertsImpl(AlertsService alerts)` Replace the default AlertsService with a custom implementation.
`WorkspaceClient`	`withAppsAPI(AppsAPI apps)` Replace the default AppsAPI with a custom implementation.
`WorkspaceClient`	`withAppsImpl(AppsService apps)` Replace the default AppsService with a custom implementation.
`WorkspaceClient`	`withArtifactAllowlistsAPI(ArtifactAllowlistsAPI artifactAllowlists)` Replace the default ArtifactAllowlistsAPI with a custom implementation.
`WorkspaceClient`	`withArtifactAllowlistsImpl(ArtifactAllowlistsService artifactAllowlists)` Replace the default ArtifactAllowlistsService with a custom implementation.
`WorkspaceClient`	`withCatalogsAPI(CatalogsAPI catalogs)` Replace the default CatalogsAPI with a custom implementation.
`WorkspaceClient`	`withCatalogsImpl(CatalogsService catalogs)` Replace the default CatalogsService with a custom implementation.
`WorkspaceClient`	`withCleanRoomsAPI(CleanRoomsAPI cleanRooms)` Replace the default CleanRoomsAPI with a custom implementation.
`WorkspaceClient`	`withCleanRoomsImpl(CleanRoomsService cleanRooms)` Replace the default CleanRoomsService with a custom implementation.
`WorkspaceClient`	`withClusterPoliciesAPI(ClusterPoliciesAPI clusterPolicies)` Replace the default ClusterPoliciesAPI with a custom implementation.
`WorkspaceClient`	`withClusterPoliciesImpl(ClusterPoliciesService clusterPolicies)` Replace the default ClusterPoliciesService with a custom implementation.
`WorkspaceClient`	`withClustersAPI(ClustersExt clusters)` Replace the default ClustersAPI with a custom implementation.
`WorkspaceClient`	`withClustersImpl(ClustersService clusters)` Replace the default ClustersService with a custom implementation.
`WorkspaceClient`	`withCommandExecutionAPI(CommandExecutionAPI commandExecution)` Replace the default CommandExecutionAPI with a custom implementation.
`WorkspaceClient`	`withCommandExecutionImpl(CommandExecutionService commandExecution)` Replace the default CommandExecutionService with a custom implementation.
`WorkspaceClient`	`withConnectionsAPI(ConnectionsAPI connections)` Replace the default ConnectionsAPI with a custom implementation.
`WorkspaceClient`	`withConnectionsImpl(ConnectionsService connections)` Replace the default ConnectionsService with a custom implementation.
`WorkspaceClient`	`withConsumerFulfillmentsAPI(ConsumerFulfillmentsAPI consumerFulfillments)` Replace the default ConsumerFulfillmentsAPI with a custom implementation.
`WorkspaceClient`	`withConsumerFulfillmentsImpl(ConsumerFulfillmentsService consumerFulfillments)` Replace the default ConsumerFulfillmentsService with a custom implementation.
`WorkspaceClient`	`withConsumerInstallationsAPI(ConsumerInstallationsAPI consumerInstallations)` Replace the default ConsumerInstallationsAPI with a custom implementation.
`WorkspaceClient`	`withConsumerInstallationsImpl(ConsumerInstallationsService consumerInstallations)` Replace the default ConsumerInstallationsService with a custom implementation.
`WorkspaceClient`	`withConsumerListingsAPI(ConsumerListingsAPI consumerListings)` Replace the default ConsumerListingsAPI with a custom implementation.
`WorkspaceClient`	`withConsumerListingsImpl(ConsumerListingsService consumerListings)` Replace the default ConsumerListingsService with a custom implementation.
`WorkspaceClient`	`withConsumerPersonalizationRequestsAPI(ConsumerPersonalizationRequestsAPI consumerPersonalizationRequests)` Replace the default ConsumerPersonalizationRequestsAPI with a custom implementation.
`WorkspaceClient`	`withConsumerPersonalizationRequestsImpl(ConsumerPersonalizationRequestsService consumerPersonalizationRequests)` Replace the default ConsumerPersonalizationRequestsService with a custom implementation.
`WorkspaceClient`	`withConsumerProvidersAPI(ConsumerProvidersAPI consumerProviders)` Replace the default ConsumerProvidersAPI with a custom implementation.
`WorkspaceClient`	`withConsumerProvidersImpl(ConsumerProvidersService consumerProviders)` Replace the default ConsumerProvidersService with a custom implementation.
`WorkspaceClient`	`withCredentialsManagerAPI(CredentialsManagerAPI credentialsManager)` Replace the default CredentialsManagerAPI with a custom implementation.
`WorkspaceClient`	`withCredentialsManagerImpl(CredentialsManagerService credentialsManager)` Replace the default CredentialsManagerService with a custom implementation.
`WorkspaceClient`	`withCurrentUserAPI(CurrentUserAPI currentUser)` Replace the default CurrentUserAPI with a custom implementation.
`WorkspaceClient`	`withCurrentUserImpl(CurrentUserService currentUser)` Replace the default CurrentUserService with a custom implementation.
`WorkspaceClient`	`withDashboardsAPI(DashboardsAPI dashboards)` Replace the default DashboardsAPI with a custom implementation.
`WorkspaceClient`	`withDashboardsImpl(DashboardsService dashboards)` Replace the default DashboardsService with a custom implementation.
`WorkspaceClient`	`withDashboardWidgetsAPI(DashboardWidgetsAPI dashboardWidgets)` Replace the default DashboardWidgetsAPI with a custom implementation.
`WorkspaceClient`	`withDashboardWidgetsImpl(DashboardWidgetsService dashboardWidgets)` Replace the default DashboardWidgetsService with a custom implementation.
`WorkspaceClient`	`withDataSourcesAPI(DataSourcesAPI dataSources)` Replace the default DataSourcesAPI with a custom implementation.
`WorkspaceClient`	`withDataSourcesImpl(DataSourcesService dataSources)` Replace the default DataSourcesService with a custom implementation.
`WorkspaceClient`	`withDbfsAPI(DbfsExt dbfs)` Replace the default DbfsAPI with a custom implementation.
`WorkspaceClient`	`withDbfsImpl(DbfsService dbfs)` Replace the default DbfsService with a custom implementation.
`WorkspaceClient`	`withDbsqlPermissionsAPI(DbsqlPermissionsAPI dbsqlPermissions)` Replace the default DbsqlPermissionsAPI with a custom implementation.
`WorkspaceClient`	`withDbsqlPermissionsImpl(DbsqlPermissionsService dbsqlPermissions)` Replace the default DbsqlPermissionsService with a custom implementation.
`WorkspaceClient`	`withExperimentsAPI(ExperimentsAPI experiments)` Replace the default ExperimentsAPI with a custom implementation.
`WorkspaceClient`	`withExperimentsImpl(ExperimentsService experiments)` Replace the default ExperimentsService with a custom implementation.
`WorkspaceClient`	`withExternalLocationsAPI(ExternalLocationsAPI externalLocations)` Replace the default ExternalLocationsAPI with a custom implementation.
`WorkspaceClient`	`withExternalLocationsImpl(ExternalLocationsService externalLocations)` Replace the default ExternalLocationsService with a custom implementation.
`WorkspaceClient`	`withFilesAPI(FilesAPI files)` Replace the default FilesAPI with a custom implementation.
`WorkspaceClient`	`withFilesImpl(FilesService files)` Replace the default FilesService with a custom implementation.
`WorkspaceClient`	`withFunctionsAPI(FunctionsAPI functions)` Replace the default FunctionsAPI with a custom implementation.
`WorkspaceClient`	`withFunctionsImpl(FunctionsService functions)` Replace the default FunctionsService with a custom implementation.
`WorkspaceClient`	`withGitCredentialsAPI(GitCredentialsAPI gitCredentials)` Replace the default GitCredentialsAPI with a custom implementation.
`WorkspaceClient`	`withGitCredentialsImpl(GitCredentialsService gitCredentials)` Replace the default GitCredentialsService with a custom implementation.
`WorkspaceClient`	`withGlobalInitScriptsAPI(GlobalInitScriptsAPI globalInitScripts)` Replace the default GlobalInitScriptsAPI with a custom implementation.
`WorkspaceClient`	`withGlobalInitScriptsImpl(GlobalInitScriptsService globalInitScripts)` Replace the default GlobalInitScriptsService with a custom implementation.
`WorkspaceClient`	`withGrantsAPI(GrantsAPI grants)` Replace the default GrantsAPI with a custom implementation.
`WorkspaceClient`	`withGrantsImpl(GrantsService grants)` Replace the default GrantsService with a custom implementation.
`WorkspaceClient`	`withGroupsAPI(GroupsAPI groups)` Replace the default GroupsAPI with a custom implementation.
`WorkspaceClient`	`withGroupsImpl(GroupsService groups)` Replace the default GroupsService with a custom implementation.
`WorkspaceClient`	`withInstancePoolsAPI(InstancePoolsAPI instancePools)` Replace the default InstancePoolsAPI with a custom implementation.
`WorkspaceClient`	`withInstancePoolsImpl(InstancePoolsService instancePools)` Replace the default InstancePoolsService with a custom implementation.
`WorkspaceClient`	`withInstanceProfilesAPI(InstanceProfilesAPI instanceProfiles)` Replace the default InstanceProfilesAPI with a custom implementation.
`WorkspaceClient`	`withInstanceProfilesImpl(InstanceProfilesService instanceProfiles)` Replace the default InstanceProfilesService with a custom implementation.
`WorkspaceClient`	`withIpAccessListsAPI(IpAccessListsAPI ipAccessLists)` Replace the default IpAccessListsAPI with a custom implementation.
`WorkspaceClient`	`withIpAccessListsImpl(IpAccessListsService ipAccessLists)` Replace the default IpAccessListsService with a custom implementation.
`WorkspaceClient`	`withJobsAPI(JobsAPI jobs)` Replace the default JobsAPI with a custom implementation.
`WorkspaceClient`	`withJobsImpl(JobsService jobs)` Replace the default JobsService with a custom implementation.
`WorkspaceClient`	`withLakehouseMonitorsAPI(LakehouseMonitorsAPI lakehouseMonitors)` Replace the default LakehouseMonitorsAPI with a custom implementation.
`WorkspaceClient`	`withLakehouseMonitorsImpl(LakehouseMonitorsService lakehouseMonitors)` Replace the default LakehouseMonitorsService with a custom implementation.
`WorkspaceClient`	`withLakeviewAPI(LakeviewAPI lakeview)` Replace the default LakeviewAPI with a custom implementation.
`WorkspaceClient`	`withLakeviewImpl(LakeviewService lakeview)` Replace the default LakeviewService with a custom implementation.
`WorkspaceClient`	`withLibrariesAPI(LibrariesAPI libraries)` Replace the default LibrariesAPI with a custom implementation.
`WorkspaceClient`	`withLibrariesImpl(LibrariesService libraries)` Replace the default LibrariesService with a custom implementation.
`WorkspaceClient`	`withMetastoresAPI(MetastoresAPI metastores)` Replace the default MetastoresAPI with a custom implementation.
`WorkspaceClient`	`withMetastoresImpl(MetastoresService metastores)` Replace the default MetastoresService with a custom implementation.
`WorkspaceClient`	`withModelRegistryAPI(ModelRegistryAPI modelRegistry)` Replace the default ModelRegistryAPI with a custom implementation.
`WorkspaceClient`	`withModelRegistryImpl(ModelRegistryService modelRegistry)` Replace the default ModelRegistryService with a custom implementation.
`WorkspaceClient`	`withModelVersionsAPI(ModelVersionsAPI modelVersions)` Replace the default ModelVersionsAPI with a custom implementation.
`WorkspaceClient`	`withModelVersionsImpl(ModelVersionsService modelVersions)` Replace the default ModelVersionsService with a custom implementation.
`WorkspaceClient`	`withOnlineTablesAPI(OnlineTablesAPI onlineTables)` Replace the default OnlineTablesAPI with a custom implementation.
`WorkspaceClient`	`withOnlineTablesImpl(OnlineTablesService onlineTables)` Replace the default OnlineTablesService with a custom implementation.
`WorkspaceClient`	`withPermissionMigrationAPI(PermissionMigrationAPI permissionMigration)` Replace the default PermissionMigrationAPI with a custom implementation.
`WorkspaceClient`	`withPermissionMigrationImpl(PermissionMigrationService permissionMigration)` Replace the default PermissionMigrationService with a custom implementation.
`WorkspaceClient`	`withPermissionsAPI(PermissionsAPI permissions)` Replace the default PermissionsAPI with a custom implementation.
`WorkspaceClient`	`withPermissionsImpl(PermissionsService permissions)` Replace the default PermissionsService with a custom implementation.
`WorkspaceClient`	`withPipelinesAPI(PipelinesAPI pipelines)` Replace the default PipelinesAPI with a custom implementation.
`WorkspaceClient`	`withPipelinesImpl(PipelinesService pipelines)` Replace the default PipelinesService with a custom implementation.
`WorkspaceClient`	`withPolicyFamiliesAPI(PolicyFamiliesAPI policyFamilies)` Replace the default PolicyFamiliesAPI with a custom implementation.
`WorkspaceClient`	`withPolicyFamiliesImpl(PolicyFamiliesService policyFamilies)` Replace the default PolicyFamiliesService with a custom implementation.
`WorkspaceClient`	`withProviderExchangeFiltersAPI(ProviderExchangeFiltersAPI providerExchangeFilters)` Replace the default ProviderExchangeFiltersAPI with a custom implementation.
`WorkspaceClient`	`withProviderExchangeFiltersImpl(ProviderExchangeFiltersService providerExchangeFilters)` Replace the default ProviderExchangeFiltersService with a custom implementation.
`WorkspaceClient`	`withProviderExchangesAPI(ProviderExchangesAPI providerExchanges)` Replace the default ProviderExchangesAPI with a custom implementation.
`WorkspaceClient`	`withProviderExchangesImpl(ProviderExchangesService providerExchanges)` Replace the default ProviderExchangesService with a custom implementation.
`WorkspaceClient`	`withProviderFilesAPI(ProviderFilesAPI providerFiles)` Replace the default ProviderFilesAPI with a custom implementation.
`WorkspaceClient`	`withProviderFilesImpl(ProviderFilesService providerFiles)` Replace the default ProviderFilesService with a custom implementation.
`WorkspaceClient`	`withProviderListingsAPI(ProviderListingsAPI providerListings)` Replace the default ProviderListingsAPI with a custom implementation.
`WorkspaceClient`	`withProviderListingsImpl(ProviderListingsService providerListings)` Replace the default ProviderListingsService with a custom implementation.
`WorkspaceClient`	`withProviderPersonalizationRequestsAPI(ProviderPersonalizationRequestsAPI providerPersonalizationRequests)` Replace the default ProviderPersonalizationRequestsAPI with a custom implementation.
`WorkspaceClient`	`withProviderPersonalizationRequestsImpl(ProviderPersonalizationRequestsService providerPersonalizationRequests)` Replace the default ProviderPersonalizationRequestsService with a custom implementation.
`WorkspaceClient`	`withProviderProviderAnalyticsDashboardsAPI(ProviderProviderAnalyticsDashboardsAPI providerProviderAnalyticsDashboards)` Replace the default ProviderProviderAnalyticsDashboardsAPI with a custom implementation.
`WorkspaceClient`	`withProviderProviderAnalyticsDashboardsImpl(ProviderProviderAnalyticsDashboardsService providerProviderAnalyticsDashboards)` Replace the default ProviderProviderAnalyticsDashboardsService with a custom implementation.
`WorkspaceClient`	`withProviderProvidersAPI(ProviderProvidersAPI providerProviders)` Replace the default ProviderProvidersAPI with a custom implementation.
`WorkspaceClient`	`withProviderProvidersImpl(ProviderProvidersService providerProviders)` Replace the default ProviderProvidersService with a custom implementation.
`WorkspaceClient`	`withProvidersAPI(ProvidersAPI providers)` Replace the default ProvidersAPI with a custom implementation.
`WorkspaceClient`	`withProvidersImpl(ProvidersService providers)` Replace the default ProvidersService with a custom implementation.
`WorkspaceClient`	`withQueriesAPI(QueriesAPI queries)` Replace the default QueriesAPI with a custom implementation.
`WorkspaceClient`	`withQueriesImpl(QueriesService queries)` Replace the default QueriesService with a custom implementation.
`WorkspaceClient`	`withQueryHistoryAPI(QueryHistoryAPI queryHistory)` Replace the default QueryHistoryAPI with a custom implementation.
`WorkspaceClient`	`withQueryHistoryImpl(QueryHistoryService queryHistory)` Replace the default QueryHistoryService with a custom implementation.
`WorkspaceClient`	`withQueryVisualizationsAPI(QueryVisualizationsAPI queryVisualizations)` Replace the default QueryVisualizationsAPI with a custom implementation.
`WorkspaceClient`	`withQueryVisualizationsImpl(QueryVisualizationsService queryVisualizations)` Replace the default QueryVisualizationsService with a custom implementation.
`WorkspaceClient`	`withRecipientActivationAPI(RecipientActivationAPI recipientActivation)` Replace the default RecipientActivationAPI with a custom implementation.
`WorkspaceClient`	`withRecipientActivationImpl(RecipientActivationService recipientActivation)` Replace the default RecipientActivationService with a custom implementation.
`WorkspaceClient`	`withRecipientsAPI(RecipientsAPI recipients)` Replace the default RecipientsAPI with a custom implementation.
`WorkspaceClient`	`withRecipientsImpl(RecipientsService recipients)` Replace the default RecipientsService with a custom implementation.
`WorkspaceClient`	`withRegisteredModelsAPI(RegisteredModelsAPI registeredModels)` Replace the default RegisteredModelsAPI with a custom implementation.
`WorkspaceClient`	`withRegisteredModelsImpl(RegisteredModelsService registeredModels)` Replace the default RegisteredModelsService with a custom implementation.
`WorkspaceClient`	`withReposAPI(ReposAPI repos)` Replace the default ReposAPI with a custom implementation.
`WorkspaceClient`	`withReposImpl(ReposService repos)` Replace the default ReposService with a custom implementation.
`WorkspaceClient`	`withSchemasAPI(SchemasAPI schemas)` Replace the default SchemasAPI with a custom implementation.
`WorkspaceClient`	`withSchemasImpl(SchemasService schemas)` Replace the default SchemasService with a custom implementation.
`WorkspaceClient`	`withSecretsAPI(SecretsExt secrets)` Replace the default SecretsAPI with a custom implementation.
`WorkspaceClient`	`withSecretsImpl(SecretsService secrets)` Replace the default SecretsService with a custom implementation.
`WorkspaceClient`	`withServicePrincipalsAPI(ServicePrincipalsAPI servicePrincipals)` Replace the default ServicePrincipalsAPI with a custom implementation.
`WorkspaceClient`	`withServicePrincipalsImpl(ServicePrincipalsService servicePrincipals)` Replace the default ServicePrincipalsService with a custom implementation.
`WorkspaceClient`	`withServingEndpointsAPI(ServingEndpointsAPI servingEndpoints)` Replace the default ServingEndpointsAPI with a custom implementation.
`WorkspaceClient`	`withServingEndpointsImpl(ServingEndpointsService servingEndpoints)` Replace the default ServingEndpointsService with a custom implementation.
`WorkspaceClient`	`withSettingsAPI(SettingsAPI settings)` Replace the default SettingsAPI with a custom implementation.
`WorkspaceClient`	`withSettingsImpl(SettingsService settings)` Replace the default SettingsService with a custom implementation.
`WorkspaceClient`	`withSharesAPI(SharesAPI shares)` Replace the default SharesAPI with a custom implementation.
`WorkspaceClient`	`withSharesImpl(SharesService shares)` Replace the default SharesService with a custom implementation.
`WorkspaceClient`	`withStatementExecutionAPI(StatementExecutionAPI statementExecution)` Replace the default StatementExecutionAPI with a custom implementation.
`WorkspaceClient`	`withStatementExecutionImpl(StatementExecutionService statementExecution)` Replace the default StatementExecutionService with a custom implementation.
`WorkspaceClient`	`withStorageCredentialsAPI(StorageCredentialsAPI storageCredentials)` Replace the default StorageCredentialsAPI with a custom implementation.
`WorkspaceClient`	`withStorageCredentialsImpl(StorageCredentialsService storageCredentials)` Replace the default StorageCredentialsService with a custom implementation.
`WorkspaceClient`	`withSystemSchemasAPI(SystemSchemasAPI systemSchemas)` Replace the default SystemSchemasAPI with a custom implementation.
`WorkspaceClient`	`withSystemSchemasImpl(SystemSchemasService systemSchemas)` Replace the default SystemSchemasService with a custom implementation.
`WorkspaceClient`	`withTableConstraintsAPI(TableConstraintsAPI tableConstraints)` Replace the default TableConstraintsAPI with a custom implementation.
`WorkspaceClient`	`withTableConstraintsImpl(TableConstraintsService tableConstraints)` Replace the default TableConstraintsService with a custom implementation.
`WorkspaceClient`	`withTablesAPI(TablesAPI tables)` Replace the default TablesAPI with a custom implementation.
`WorkspaceClient`	`withTablesImpl(TablesService tables)` Replace the default TablesService with a custom implementation.
`WorkspaceClient`	`withTokenManagementAPI(TokenManagementAPI tokenManagement)` Replace the default TokenManagementAPI with a custom implementation.
`WorkspaceClient`	`withTokenManagementImpl(TokenManagementService tokenManagement)` Replace the default TokenManagementService with a custom implementation.
`WorkspaceClient`	`withTokensAPI(TokensAPI tokens)` Replace the default TokensAPI with a custom implementation.
`WorkspaceClient`	`withTokensImpl(TokensService tokens)` Replace the default TokensService with a custom implementation.
`WorkspaceClient`	`withUsersAPI(UsersAPI users)` Replace the default UsersAPI with a custom implementation.
`WorkspaceClient`	`withUsersImpl(UsersService users)` Replace the default UsersService with a custom implementation.
`WorkspaceClient`	`withVectorSearchEndpointsAPI(VectorSearchEndpointsAPI vectorSearchEndpoints)` Replace the default VectorSearchEndpointsAPI with a custom implementation.
`WorkspaceClient`	`withVectorSearchEndpointsImpl(VectorSearchEndpointsService vectorSearchEndpoints)` Replace the default VectorSearchEndpointsService with a custom implementation.
`WorkspaceClient`	`withVectorSearchIndexesAPI(VectorSearchIndexesAPI vectorSearchIndexes)` Replace the default VectorSearchIndexesAPI with a custom implementation.
`WorkspaceClient`	`withVectorSearchIndexesImpl(VectorSearchIndexesService vectorSearchIndexes)` Replace the default VectorSearchIndexesService with a custom implementation.
`WorkspaceClient`	`withVolumesAPI(VolumesAPI volumes)` Replace the default VolumesAPI with a custom implementation.
`WorkspaceClient`	`withVolumesImpl(VolumesService volumes)` Replace the default VolumesService with a custom implementation.
`WorkspaceClient`	`withWarehousesAPI(WarehousesAPI warehouses)` Replace the default WarehousesAPI with a custom implementation.
`WorkspaceClient`	`withWarehousesImpl(WarehousesService warehouses)` Replace the default WarehousesService with a custom implementation.
`WorkspaceClient`	`withWorkspaceAPI(WorkspaceAPI workspace)` Replace the default WorkspaceAPI with a custom implementation.
`WorkspaceClient`	`withWorkspaceBindingsAPI(WorkspaceBindingsAPI workspaceBindings)` Replace the default WorkspaceBindingsAPI with a custom implementation.
`WorkspaceClient`	`withWorkspaceBindingsImpl(WorkspaceBindingsService workspaceBindings)` Replace the default WorkspaceBindingsService with a custom implementation.
`WorkspaceClient`	`withWorkspaceConfAPI(WorkspaceConfAPI workspaceConf)` Replace the default WorkspaceConfAPI with a custom implementation.
`WorkspaceClient`	`withWorkspaceConfImpl(WorkspaceConfService workspaceConf)` Replace the default WorkspaceConfService with a custom implementation.
`WorkspaceClient`	`withWorkspaceImpl(WorkspaceService workspace)` Replace the default WorkspaceService with a custom implementation.
`WorkspaceAPI`	`workspace()` The Workspace API allows you to list, import, export, and delete notebooks and folders.
`WorkspaceBindingsAPI`	`workspaceBindings()` A securable in Databricks can be configured as __OPEN__ or __ISOLATED__.
`WorkspaceConfAPI`	`workspaceConf()` This API allows updating known workspace settings for advanced users.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - WorkspaceClient
```
public WorkspaceClient()
```
  - WorkspaceClient
```
public WorkspaceClient(DatabricksConfig config)
```
  - WorkspaceClient
```
public WorkspaceClient(boolean mock)
```
    Constructor for mocks
  - WorkspaceClient
```
public WorkspaceClient(boolean mock,
                       ApiClient apiClient)
```
    Constructor for mocks
- Method Detail
  - accountAccessControlProxy
```
public AccountAccessControlProxyAPI accountAccessControlProxy()
```
    These APIs manage access rules on resources in an account. Currently, only grant rules are supported. A grant rule specifies a role assigned to a set of principals. A list of rules attached to a resource is called a rule set. A workspace must belong to an account for these APIs to work.
  - alerts
```
public AlertsAPI alerts()
```
    The alerts API can be used to perform CRUD operations on alerts. An alert is a Databricks SQL object that periodically runs a query, evaluates a condition of its result, and notifies one or more users and/or notification destinations if the condition was met. Alerts can be scheduled using the `sql_task` type of the Jobs API, e.g. :method:jobs/create.
  - apps
```
public AppsAPI apps()
```
    Lakehouse Apps run directly on a customer’s Databricks instance, integrate with their data, use and extend Databricks services, and enable users to interact through single sign-on.
  - artifactAllowlists
```
public ArtifactAllowlistsAPI artifactAllowlists()
```
    In Databricks Runtime 13.3 and above, you can add libraries and init scripts to the `allowlist` in UC so that users can leverage these artifacts on compute configured with shared access mode.
  - catalogs
```
public CatalogsAPI catalogs()
```
    A catalog is the first layer of Unity Catalog’s three-level namespace. It’s used to organize your data assets. Users can see all catalogs on which they have been assigned the USE_CATALOG data permission.
    In Unity Catalog, admins and data stewards manage users and their access to data centrally across all of the workspaces in a Databricks account. Users in different workspaces can share access to the same data, depending on privileges granted centrally in Unity Catalog.
  - cleanRooms
```
public CleanRoomsAPI cleanRooms()
```
    A clean room is a secure, privacy-protecting environment where two or more parties can share sensitive enterprise data, including customer data, for measurements, insights, activation and other use cases.
    To create clean rooms, you must be a metastore admin or a user with the **CREATE_CLEAN_ROOM** privilege.
  - clusterPolicies
```
public ClusterPoliciesAPI clusterPolicies()
```
    You can use cluster policies to control users' ability to configure clusters based on a set of rules. These rules specify which attributes or attribute values can be used during cluster creation. Cluster policies have ACLs that limit their use to specific users and groups.
    With cluster policies, you can: - Auto-install cluster libraries on the next restart by listing them in the policy's "libraries" field (Public Preview). - Limit users to creating clusters with the prescribed settings. - Simplify the user interface, enabling more users to create clusters, by fixing and hiding some fields. - Manage costs by setting limits on attributes that impact the hourly rate.
    Cluster policy permissions limit which policies a user can select in the Policy drop-down when the user creates a cluster: - A user who has unrestricted cluster create permission can select the Unrestricted policy and create fully-configurable clusters. - A user who has both unrestricted cluster create permission and access to cluster policies can select the Unrestricted policy and policies they have access to. - A user that has access to only cluster policies, can select the policies they have access to.
    If no policies exist in the workspace, the Policy drop-down doesn't appear. Only admin users can create, edit, and delete policies. Admin users also have access to all policies.
  - clusters
```
public ClustersExt clusters()
```
    The Clusters API allows you to create, start, edit, list, terminate, and delete clusters.
    Databricks maps cluster node instance types to compute units known as DBUs. See the instance type pricing page for a list of the supported instance types and their corresponding DBUs.
    A Databricks cluster is a set of computation resources and configurations on which you run data engineering, data science, and data analytics workloads, such as production ETL pipelines, streaming analytics, ad-hoc analytics, and machine learning.
    You run these workloads as a set of commands in a notebook or as an automated job. Databricks makes a distinction between all-purpose clusters and job clusters. You use all-purpose clusters to analyze data collaboratively using interactive notebooks. You use job clusters to run fast and robust automated jobs.
    You can create an all-purpose cluster using the UI, CLI, or REST API. You can manually terminate and restart an all-purpose cluster. Multiple users can share such clusters to do collaborative interactive analysis.
    IMPORTANT: Databricks retains cluster configuration information for up to 200 all-purpose clusters terminated in the last 30 days and up to 30 job clusters recently terminated by the job scheduler. To keep an all-purpose cluster configuration even after it has been terminated for more than 30 days, an administrator can pin a cluster to the cluster list.
  - commandExecution
```
public CommandExecutionAPI commandExecution()
```
    This API allows execution of Python, Scala, SQL, or R commands on running Databricks Clusters.
  - connections
```
public ConnectionsAPI connections()
```
    Connections allow for creating a connection to an external data source.
    A connection is an abstraction of an external data source that can be connected from Databricks Compute. Creating a connection object is the first step to managing external data sources within Unity Catalog, with the second step being creating a data object (catalog, schema, or table) using the connection. Data objects derived from a connection can be written to or read from similar to other Unity Catalog data objects based on cloud storage. Users may create different types of connections with each connection having a unique set of configuration options to support credential management and other settings.
  - consumerFulfillments
```
public ConsumerFulfillmentsAPI consumerFulfillments()
```
    Fulfillments are entities that allow consumers to preview installations.
  - consumerInstallations
```
public ConsumerInstallationsAPI consumerInstallations()
```
    Installations are entities that allow consumers to interact with Databricks Marketplace listings.
  - consumerListings
```
public ConsumerListingsAPI consumerListings()
```
    Listings are the core entities in the Marketplace. They represent the products that are available for consumption.
  - consumerPersonalizationRequests
```
public ConsumerPersonalizationRequestsAPI consumerPersonalizationRequests()
```
    Personalization Requests allow customers to interact with the individualized Marketplace listing flow.
  - consumerProviders
```
public ConsumerProvidersAPI consumerProviders()
```
    Providers are the entities that publish listings to the Marketplace.
  - credentialsManager
```
public CredentialsManagerAPI credentialsManager()
```
    Credentials manager interacts with with Identity Providers to to perform token exchanges using stored credentials and refresh tokens.
  - currentUser
```
public CurrentUserAPI currentUser()
```
    This API allows retrieving information about currently authenticated user or service principal.
  - dashboardWidgets
```
public DashboardWidgetsAPI dashboardWidgets()
```
    This is an evolving API that facilitates the addition and removal of widgets from existing dashboards within the Databricks Workspace. Data structures may change over time.
  - dashboards
```
public DashboardsAPI dashboards()
```
    In general, there is little need to modify dashboards using the API. However, it can be useful to use dashboard objects to look-up a collection of related query IDs. The API can also be used to duplicate multiple dashboards at once since you can get a dashboard definition with a GET request and then POST it to create a new one. Dashboards can be scheduled using the `sql_task` type of the Jobs API, e.g. :method:jobs/create.
  - dataSources
```
public DataSourcesAPI dataSources()
```
    This API is provided to assist you in making new query objects. When creating a query object, you may optionally specify a `data_source_id` for the SQL warehouse against which it will run. If you don't already know the `data_source_id` for your desired SQL warehouse, this API will help you find it.
    This API does not support searches. It returns the full list of SQL warehouses in your workspace. We advise you to use any text editor, REST client, or `grep` to search the response from this API for the name of your SQL warehouse as it appears in Databricks SQL.
  - dbfs
```
public DbfsExt dbfs()
```
    DBFS API makes it simple to interact with various data sources without having to include a users credentials every time to read a file.
  - dbsqlPermissions
```
public DbsqlPermissionsAPI dbsqlPermissions()
```
    The SQL Permissions API is similar to the endpoints of the :method:permissions/set. However, this exposes only one endpoint, which gets the Access Control List for a given object. You cannot modify any permissions using this API.
    There are three levels of permission:
    - `CAN_VIEW`: Allows read-only access
    - `CAN_RUN`: Allows read access and run access (superset of `CAN_VIEW`)
    - `CAN_MANAGE`: Allows all actions: read, run, edit, delete, modify permissions (superset of `CAN_RUN`)
  - experiments
```
public ExperimentsAPI experiments()
```
    Experiments are the primary unit of organization in MLflow; all MLflow runs belong to an experiment. Each experiment lets you visualize, search, and compare runs, as well as download run artifacts or metadata for analysis in other tools. Experiments are maintained in a Databricks hosted MLflow tracking server.
    Experiments are located in the workspace file tree. You manage experiments using the same tools you use to manage other workspace objects such as folders, notebooks, and libraries.
  - externalLocations
```
public ExternalLocationsAPI externalLocations()
```
    An external location is an object that combines a cloud storage path with a storage credential that authorizes access to the cloud storage path. Each external location is subject to Unity Catalog access-control policies that control which users and groups can access the credential. If a user does not have access to an external location in Unity Catalog, the request fails and Unity Catalog does not attempt to authenticate to your cloud tenant on the user’s behalf.
    Databricks recommends using external locations rather than using storage credentials directly.
    To create external locations, you must be a metastore admin or a user with the **CREATE_EXTERNAL_LOCATION** privilege.
  - files
```
public FilesAPI files()
```
    The Files API is a standard HTTP API that allows you to read, write, list, and delete files and directories by referring to their URI. The API makes working with file content as raw bytes easier and more efficient.
    The API supports [Unity Catalog volumes], where files and directories to operate on are specified using their volume URI path, which follows the format /Volumes/<catalog_name>/<schema_name>/<volume_name>/<path_to_file>.
    The Files API has two distinct endpoints, one for working with files (`/fs/files`) and another one for working with directories (`/fs/directories`). Both endpoints, use the standard HTTP methods GET, HEAD, PUT, and DELETE to manage files and directories specified using their URI path. The path is always absolute.
    [Unity Catalog volumes]: https://docs.databricks.com/en/connect/unity-catalog/volumes.html
  - functions
```
public FunctionsAPI functions()
```
    Functions implement User-Defined Functions (UDFs) in Unity Catalog.
    The function implementation can be any SQL expression or Query, and it can be invoked wherever a table reference is allowed in a query. In Unity Catalog, a function resides at the same level as a table, so it can be referenced with the form __catalog_name__.__schema_name__.__function_name__.
  - gitCredentials
```
public GitCredentialsAPI gitCredentials()
```
    Registers personal access token for Databricks to do operations on behalf of the user.
    See [more info].
    [more info]: https://docs.databricks.com/repos/get-access-tokens-from-git-provider.html
  - globalInitScripts
```
public GlobalInitScriptsAPI globalInitScripts()
```
    The Global Init Scripts API enables Workspace administrators to configure global initialization scripts for their workspace. These scripts run on every node in every cluster in the workspace.
    **Important:** Existing clusters must be restarted to pick up any changes made to global init scripts. Global init scripts are run in order. If the init script returns with a bad exit code, the Apache Spark container fails to launch and init scripts with later position are skipped. If enough containers fail, the entire cluster fails with a `GLOBAL_INIT_SCRIPT_FAILURE` error code.
  - grants
```
public GrantsAPI grants()
```
    In Unity Catalog, data is secure by default. Initially, users have no access to data in a metastore. Access can be granted by either a metastore admin, the owner of an object, or the owner of the catalog or schema that contains the object. Securable objects in Unity Catalog are hierarchical and privileges are inherited downward.
    Securable objects in Unity Catalog are hierarchical and privileges are inherited downward. This means that granting a privilege on the catalog automatically grants the privilege to all current and future objects within the catalog. Similarly, privileges granted on a schema are inherited by all current and future objects within that schema.
  - groups
```
public GroupsAPI groups()
```
    Groups simplify identity management, making it easier to assign access to Databricks workspace, data, and other securable objects.
    It is best practice to assign access to workspaces and access-control policies in Unity Catalog to groups, instead of to users individually. All Databricks workspace identities can be assigned as members of groups, and members inherit permissions that are assigned to their group.
  - instancePools
```
public InstancePoolsAPI instancePools()
```
    Instance Pools API are used to create, edit, delete and list instance pools by using ready-to-use cloud instances which reduces a cluster start and auto-scaling times.
    Databricks pools reduce cluster start and auto-scaling times by maintaining a set of idle, ready-to-use instances. When a cluster is attached to a pool, cluster nodes are created using the pool’s idle instances. If the pool has no idle instances, the pool expands by allocating a new instance from the instance provider in order to accommodate the cluster’s request. When a cluster releases an instance, it returns to the pool and is free for another cluster to use. Only clusters attached to a pool can use that pool’s idle instances.
    You can specify a different pool for the driver node and worker nodes, or use the same pool for both.
    Databricks does not charge DBUs while instances are idle in the pool. Instance provider billing does apply. See pricing.
  - instanceProfiles
```
public InstanceProfilesAPI instanceProfiles()
```
    The Instance Profiles API allows admins to add, list, and remove instance profiles that users can launch clusters with. Regular users can list the instance profiles available to them. See [Secure access to S3 buckets] using instance profiles for more information.
    [Secure access to S3 buckets]: https://docs.databricks.com/administration-guide/cloud-configurations/aws/instance-profiles.html
  - ipAccessLists
```
public IpAccessListsAPI ipAccessLists()
```
    IP Access List enables admins to configure IP access lists.
    IP access lists affect web application access and REST API access to this workspace only. If the feature is disabled for a workspace, all access is allowed for this workspace. There is support for allow lists (inclusion) and block lists (exclusion).
    When a connection is attempted: 1. **First, all block lists are checked.** If the connection IP address matches any block list, the connection is rejected. 2. **If the connection was not rejected by block lists**, the IP address is compared with the allow lists.
    If there is at least one allow list for the workspace, the connection is allowed only if the IP address matches an allow list. If there are no allow lists for the workspace, all IP addresses are allowed.
    For all allow lists and block lists combined, the workspace supports a maximum of 1000 IP/CIDR values, where one CIDR counts as a single value.
    After changes to the IP access list feature, it can take a few minutes for changes to take effect.
  - jobs
```
public JobsAPI jobs()
```
    The Jobs API allows you to create, edit, and delete jobs.
    You can use a Databricks job to run a data processing or data analysis task in a Databricks cluster with scalable resources. Your job can consist of a single task or can be a large, multi-task workflow with complex dependencies. Databricks manages the task orchestration, cluster management, monitoring, and error reporting for all of your jobs. You can run your jobs immediately or periodically through an easy-to-use scheduling system. You can implement job tasks using notebooks, JARS, Delta Live Tables pipelines, or Python, Scala, Spark submit, and Java applications.
    You should never hard code secrets or store them in plain text. Use the [Secrets CLI] to manage secrets in the [Databricks CLI]. Use the [Secrets utility] to reference secrets in notebooks and jobs.
    [Databricks CLI]: https://docs.databricks.com/dev-tools/cli/index.html [Secrets CLI]: https://docs.databricks.com/dev-tools/cli/secrets-cli.html [Secrets utility]: https://docs.databricks.com/dev-tools/databricks-utils.html#dbutils-secrets
  - lakehouseMonitors
```
public LakehouseMonitorsAPI lakehouseMonitors()
```
    A monitor computes and monitors data or model quality metrics for a table over time. It generates metrics tables and a dashboard that you can use to monitor table health and set alerts.
    Most write operations require the user to be the owner of the table (or its parent schema or parent catalog). Viewing the dashboard, computed metrics, or monitor configuration only requires the user to have **SELECT** privileges on the table (along with **USE_SCHEMA** and **USE_CATALOG**).
  - lakeview
```
public LakeviewAPI lakeview()
```
    These APIs provide specific management operations for Lakeview dashboards. Generic resource management can be done with Workspace API (import, export, get-status, list, delete).
  - libraries
```
public LibrariesAPI libraries()
```
    The Libraries API allows you to install and uninstall libraries and get the status of libraries on a cluster.
    To make third-party or custom code available to notebooks and jobs running on your clusters, you can install a library. Libraries can be written in Python, Java, Scala, and R. You can upload Python, Java, Scala and R libraries and point to external packages in PyPI, Maven, and CRAN repositories.
    Cluster libraries can be used by all notebooks running on a cluster. You can install a cluster library directly from a public repository such as PyPI or Maven, using a previously installed workspace library, or using an init script.
    When you uninstall a library from a cluster, the library is removed only when you restart the cluster. Until you restart the cluster, the status of the uninstalled library appears as Uninstall pending restart.
  - metastores
```
public MetastoresAPI metastores()
```
    A metastore is the top-level container of objects in Unity Catalog. It stores data assets (tables and views) and the permissions that govern access to them. Databricks account admins can create metastores and assign them to Databricks workspaces to control which workloads use each metastore. For a workspace to use Unity Catalog, it must have a Unity Catalog metastore attached.
    Each metastore is configured with a root storage location in a cloud storage account. This storage location is used for metadata and managed tables data.
    NOTE: This metastore is distinct from the metastore included in Databricks workspaces created before Unity Catalog was released. If your workspace includes a legacy Hive metastore, the data in that metastore is available in a catalog named hive_metastore.
  - modelRegistry
```
public ModelRegistryAPI modelRegistry()
```
    Note: This API reference documents APIs for the Workspace Model Registry. Databricks recommends using [Models in Unity Catalog](/api/workspace/registeredmodels) instead. Models in Unity Catalog provides centralized model governance, cross-workspace access, lineage, and deployment. Workspace Model Registry will be deprecated in the future.
    The Workspace Model Registry is a centralized model repository and a UI and set of APIs that enable you to manage the full lifecycle of MLflow Models.
  - modelVersions
```
public ModelVersionsAPI modelVersions()
```
    Databricks provides a hosted version of MLflow Model Registry in Unity Catalog. Models in Unity Catalog provide centralized access control, auditing, lineage, and discovery of ML models across Databricks workspaces.
    This API reference documents the REST endpoints for managing model versions in Unity Catalog. For more details, see the [registered models API docs](/api/workspace/registeredmodels).
  - onlineTables
```
public OnlineTablesAPI onlineTables()
```
    Online tables provide lower latency and higher QPS access to data from Delta tables.
  - permissionMigration
```
public PermissionMigrationAPI permissionMigration()
```
    This spec contains undocumented permission migration APIs used in https://github.com/databrickslabs/ucx.
  - permissions
```
public PermissionsAPI permissions()
```
    Permissions API are used to create read, write, edit, update and manage access for various users on different objects and endpoints.
    * **[Cluster permissions](:service:clusters)** — Manage which users can manage, restart, or attach to clusters.
    * **[Cluster policy permissions](:service:clusterpolicies)** — Manage which users can use cluster policies.
    * **[Delta Live Tables pipeline permissions](:service:pipelines)** — Manage which users can view, manage, run, cancel, or own a Delta Live Tables pipeline.
    * **[Job permissions](:service:jobs)** — Manage which users can view, manage, trigger, cancel, or own a job.
    * **[MLflow experiment permissions](:service:experiments)** — Manage which users can read, edit, or manage MLflow experiments.
    * **[MLflow registered model permissions](:service:modelregistry)** — Manage which users can read, edit, or manage MLflow registered models.
    * **[Password permissions](:service:users)** — Manage which users can use password login when SSO is enabled.
    * **[Instance Pool permissions](:service:instancepools)** — Manage which users can manage or attach to pools.
    * **[Repo permissions](repos)** — Manage which users can read, run, edit, or manage a repo.
    * **[Serving endpoint permissions](:service:servingendpoints)** — Manage which users can view, query, or manage a serving endpoint.
    * **[SQL warehouse permissions](:service:warehouses)** — Manage which users can use or manage SQL warehouses.
    * **[Token permissions](:service:tokenmanagement)** — Manage which users can create or use tokens.
    * **[Workspace object permissions](:service:workspace)** — Manage which users can read, run, edit, or manage directories, files, and notebooks.
    For the mapping of the required permissions for specific actions or abilities and other important information, see [Access Control].
    Note that to manage access control on service principals, use **[Account Access Control Proxy](:service:accountaccesscontrolproxy)**.
    [Access Control]: https://docs.databricks.com/security/auth-authz/access-control/index.html
  - pipelines
```
public PipelinesAPI pipelines()
```
    The Delta Live Tables API allows you to create, edit, delete, start, and view details about pipelines.
    Delta Live Tables is a framework for building reliable, maintainable, and testable data processing pipelines. You define the transformations to perform on your data, and Delta Live Tables manages task orchestration, cluster management, monitoring, data quality, and error handling.
    Instead of defining your data pipelines using a series of separate Apache Spark tasks, Delta Live Tables manages how your data is transformed based on a target schema you define for each processing step. You can also enforce data quality with Delta Live Tables expectations. Expectations allow you to define expected data quality and specify how to handle records that fail those expectations.
  - policyFamilies
```
public PolicyFamiliesAPI policyFamilies()
```
    View available policy families. A policy family contains a policy definition providing best practices for configuring clusters for a particular use case.
    Databricks manages and provides policy families for several common cluster use cases. You cannot create, edit, or delete policy families.
    Policy families cannot be used directly to create clusters. Instead, you create cluster policies using a policy family. Cluster policies created using a policy family inherit the policy family's policy definition.
  - providerExchangeFilters
```
public ProviderExchangeFiltersAPI providerExchangeFilters()
```
    Marketplace exchanges filters curate which groups can access an exchange.
  - providerExchanges
```
public ProviderExchangesAPI providerExchanges()
```
    Marketplace exchanges allow providers to share their listings with a curated set of customers.
  - providerFiles
```
public ProviderFilesAPI providerFiles()
```
    Marketplace offers a set of file APIs for various purposes such as preview notebooks and provider icons.
  - providerListings
```
public ProviderListingsAPI providerListings()
```
    Listings are the core entities in the Marketplace. They represent the products that are available for consumption.
  - providerPersonalizationRequests
```
public ProviderPersonalizationRequestsAPI providerPersonalizationRequests()
```
    Personalization requests are an alternate to instantly available listings. Control the lifecycle of personalized solutions.
  - providerProviderAnalyticsDashboards
```
public ProviderProviderAnalyticsDashboardsAPI providerProviderAnalyticsDashboards()
```
    Manage templated analytics solution for providers.
  - providerProviders
```
public ProviderProvidersAPI providerProviders()
```
    Providers are entities that manage assets in Marketplace.
  - providers
```
public ProvidersAPI providers()
```
    A data provider is an object representing the organization in the real world who shares the data. A provider contains shares which further contain the shared data.
  - queries
```
public QueriesAPI queries()
```
    These endpoints are used for CRUD operations on query definitions. Query definitions include the target SQL warehouse, query text, name, description, tags, parameters, and visualizations. Queries can be scheduled using the `sql_task` type of the Jobs API, e.g. :method:jobs/create.
  - queryHistory
```
public QueryHistoryAPI queryHistory()
```
    Access the history of queries through SQL warehouses.
  - queryVisualizations
```
public QueryVisualizationsAPI queryVisualizations()
```
    This is an evolving API that facilitates the addition and removal of vizualisations from existing queries within the Databricks Workspace. Data structures may change over time.
  - recipientActivation
```
public RecipientActivationAPI recipientActivation()
```
    The Recipient Activation API is only applicable in the open sharing model where the recipient object has the authentication type of `TOKEN`. The data recipient follows the activation link shared by the data provider to download the credential file that includes the access token. The recipient will then use the credential file to establish a secure connection with the provider to receive the shared data.
    Note that you can download the credential file only once. Recipients should treat the downloaded credential as a secret and must not share it outside of their organization.
  - recipients
```
public RecipientsAPI recipients()
```
    A recipient is an object you create using :method:recipients/create to represent an organization which you want to allow access shares. The way how sharing works differs depending on whether or not your recipient has access to a Databricks workspace that is enabled for Unity Catalog:
    - For recipients with access to a Databricks workspace that is enabled for Unity Catalog, you can create a recipient object along with a unique sharing identifier you get from the recipient. The sharing identifier is the key identifier that enables the secure connection. This sharing mode is called **Databricks-to-Databricks sharing**.
    - For recipients without access to a Databricks workspace that is enabled for Unity Catalog, when you create a recipient object, Databricks generates an activation link you can send to the recipient. The recipient follows the activation link to download the credential file, and then uses the credential file to establish a secure connection to receive the shared data. This sharing mode is called **open sharing**.
  - registeredModels
```
public RegisteredModelsAPI registeredModels()
```
    Databricks provides a hosted version of MLflow Model Registry in Unity Catalog. Models in Unity Catalog provide centralized access control, auditing, lineage, and discovery of ML models across Databricks workspaces.
    An MLflow registered model resides in the third layer of Unity Catalog’s three-level namespace. Registered models contain model versions, which correspond to actual ML models (MLflow models). Creating new model versions currently requires use of the MLflow Python client. Once model versions are created, you can load them for batch inference using MLflow Python client APIs, or deploy them for real-time serving using Databricks Model Serving.
    All operations on registered models and model versions require USE_CATALOG permissions on the enclosing catalog and USE_SCHEMA permissions on the enclosing schema. In addition, the following additional privileges are required for various operations:
    * To create a registered model, users must additionally have the CREATE_MODEL permission on the target schema. * To view registered model or model version metadata, model version data files, or invoke a model version, users must additionally have the EXECUTE permission on the registered model * To update registered model or model version tags, users must additionally have APPLY TAG permissions on the registered model * To update other registered model or model version metadata (comments, aliases) create a new model version, or update permissions on the registered model, users must be owners of the registered model.
    Note: The securable type for models is "FUNCTION". When using REST APIs (e.g. tagging, grants) that specify a securable type, use "FUNCTION" as the securable type.
  - repos
```
public ReposAPI repos()
```
    The Repos API allows users to manage their git repos. Users can use the API to access all repos that they have manage permissions on.
    Databricks Repos is a visual Git client in Databricks. It supports common Git operations such a cloning a repository, committing and pushing, pulling, branch management, and visual comparison of diffs when committing.
    Within Repos you can develop code in notebooks or other files and follow data science and engineering code development best practices using Git for version control, collaboration, and CI/CD.
  - schemas
```
public SchemasAPI schemas()
```
    A schema (also called a database) is the second layer of Unity Catalog’s three-level namespace. A schema organizes tables, views and functions. To access (or list) a table or view in a schema, users must have the USE_SCHEMA data permission on the schema and its parent catalog, and they must have the SELECT permission on the table or view.
  - secrets
```
public SecretsExt secrets()
```
    The Secrets API allows you to manage secrets, secret scopes, and access permissions.
    Sometimes accessing data requires that you authenticate to external data sources through JDBC. Instead of directly entering your credentials into a notebook, use Databricks secrets to store your credentials and reference them in notebooks and jobs.
    Administrators, secret creators, and users granted permission can read Databricks secrets. While Databricks makes an effort to redact secret values that might be displayed in notebooks, it is not possible to prevent such users from reading secrets.
  - servicePrincipals
```
public ServicePrincipalsAPI servicePrincipals()
```
    Identities for use with jobs, automated tools, and systems such as scripts, apps, and CI/CD platforms. Databricks recommends creating service principals to run production jobs or modify production data. If all processes that act on production data run with service principals, interactive users do not need any write, delete, or modify privileges in production. This eliminates the risk of a user overwriting production data by accident.
  - servingEndpoints
```
public ServingEndpointsAPI servingEndpoints()
```
    The Serving Endpoints API allows you to create, update, and delete model serving endpoints.
    You can use a serving endpoint to serve models from the Databricks Model Registry or from Unity Catalog. Endpoints expose the underlying models as scalable REST API endpoints using serverless compute. This means the endpoints and associated compute resources are fully managed by Databricks and will not appear in your cloud account. A serving endpoint can consist of one or more MLflow models from the Databricks Model Registry, called served entities. A serving endpoint can have at most ten served entities. You can configure traffic settings to define how requests should be routed to your served entities behind an endpoint. Additionally, you can configure the scale of resources that should be applied to each served entity.
  - settings
```
public SettingsAPI settings()
```
    Workspace Settings API allows users to manage settings at the workspace level.
  - shares
```
public SharesAPI shares()
```
    A share is a container instantiated with :method:shares/create. Once created you can iteratively register a collection of existing data assets defined within the metastore using :method:shares/update. You can register data assets under their original name, qualified by their original schema, or provide alternate exposed names.
  - statementExecution
```
public StatementExecutionAPI statementExecution()
```
    The Databricks SQL Statement Execution API can be used to execute SQL statements on a SQL warehouse and fetch the result.
    **Getting started**
    We suggest beginning with the [Databricks SQL Statement Execution API tutorial].
    **Overview of statement execution and result fetching**
    Statement execution begins by issuing a :method:statementexecution/executeStatement request with a valid SQL statement and warehouse ID, along with optional parameters such as the data catalog and output format. If no other parameters are specified, the server will wait for up to 10s before returning a response. If the statement has completed within this timespan, the response will include the result data as a JSON array and metadata. Otherwise, if no result is available after the 10s timeout expired, the response will provide the statement ID that can be used to poll for results by using a :method:statementexecution/getStatement request.
    You can specify whether the call should behave synchronously, asynchronously or start synchronously with a fallback to asynchronous execution. This is controlled with the `wait_timeout` and `on_wait_timeout` settings. If `wait_timeout` is set between 5-50 seconds (default: 10s), the call waits for results up to the specified timeout; when set to `0s`, the call is asynchronous and responds immediately with a statement ID. The `on_wait_timeout` setting specifies what should happen when the timeout is reached while the statement execution has not yet finished. This can be set to either `CONTINUE`, to fallback to asynchronous mode, or it can be set to `CANCEL`, which cancels the statement.
    In summary: - Synchronous mode - `wait_timeout=30s` and `on_wait_timeout=CANCEL` - The call waits up to 30 seconds; if the statement execution finishes within this time, the result data is returned directly in the response. If the execution takes longer than 30 seconds, the execution is canceled and the call returns with a `CANCELED` state. - Asynchronous mode - `wait_timeout=0s` (`on_wait_timeout` is ignored) - The call doesn't wait for the statement to finish but returns directly with a statement ID. The status of the statement execution can be polled by issuing :method:statementexecution/getStatement with the statement ID. Once the execution has succeeded, this call also returns the result and metadata in the response. - Hybrid mode (default) - `wait_timeout=10s` and `on_wait_timeout=CONTINUE` - The call waits for up to 10 seconds; if the statement execution finishes within this time, the result data is returned directly in the response. If the execution takes longer than 10 seconds, a statement ID is returned. The statement ID can be used to fetch status and results in the same way as in the asynchronous mode.
    Depending on the size, the result can be split into multiple chunks. If the statement execution is successful, the statement response contains a manifest and the first chunk of the result. The manifest contains schema information and provides metadata for each chunk in the result. Result chunks can be retrieved by index with :method:statementexecution/getStatementResultChunkN which may be called in any order and in parallel. For sequential fetching, each chunk, apart from the last, also contains a `next_chunk_index` and `next_chunk_internal_link` that point to the next chunk.
    A statement can be canceled with :method:statementexecution/cancelExecution.
    **Fetching result data: format and disposition**
    To specify the format of the result data, use the `format` field, which can be set to one of the following options: `JSON_ARRAY` (JSON), `ARROW_STREAM` ([Apache Arrow Columnar]), or `CSV`.
    There are two ways to receive statement results, controlled by the `disposition` setting, which can be either `INLINE` or `EXTERNAL_LINKS`:
    - `INLINE`: In this mode, the result data is directly included in the response. It's best suited for smaller results. This mode can only be used with the `JSON_ARRAY` format.
    - `EXTERNAL_LINKS`: In this mode, the response provides links that can be used to download the result data in chunks separately. This approach is ideal for larger results and offers higher throughput. This mode can be used with all the formats: `JSON_ARRAY`, `ARROW_STREAM`, and `CSV`.
    By default, the API uses `format=JSON_ARRAY` and `disposition=INLINE`.
    **Limits and limitations**
    Note: The byte limit for INLINE disposition is based on internal storage metrics and will not exactly match the byte count of the actual payload.
    - Statements with `disposition=INLINE` are limited to 25 MiB and will fail when this limit is exceeded. - Statements with `disposition=EXTERNAL_LINKS` are limited to 100 GiB. Result sets larger than this limit will be truncated. Truncation is indicated by the `truncated` field in the result manifest. - The maximum query text size is 16 MiB. - Cancelation might silently fail. A successful response from a cancel request indicates that the cancel request was successfully received and sent to the processing engine. However, an outstanding statement might have already completed execution when the cancel request arrives. Polling for status until a terminal state is reached is a reliable way to determine the final state. - Wait timeouts are approximate, occur server-side, and cannot account for things such as caller delays and network latency from caller to service. - The system will auto-close a statement after one hour if the client stops polling and thus you must poll at least once an hour. - The results are only available for one hour after success; polling does not extend this.
    [Apache Arrow Columnar]: https://arrow.apache.org/overview/ [Databricks SQL Statement Execution API tutorial]: https://docs.databricks.com/sql/api/sql-execution-tutorial.html
  - storageCredentials
```
public StorageCredentialsAPI storageCredentials()
```
    A storage credential represents an authentication and authorization mechanism for accessing data stored on your cloud tenant. Each storage credential is subject to Unity Catalog access-control policies that control which users and groups can access the credential. If a user does not have access to a storage credential in Unity Catalog, the request fails and Unity Catalog does not attempt to authenticate to your cloud tenant on the user’s behalf.
    Databricks recommends using external locations rather than using storage credentials directly.
    To create storage credentials, you must be a Databricks account admin. The account admin who creates the storage credential can delegate ownership to another user or group to manage permissions on it.
  - systemSchemas
```
public SystemSchemasAPI systemSchemas()
```
    A system schema is a schema that lives within the system catalog. A system schema may contain information about customer usage of Unity Catalog such as audit-logs, billing-logs, lineage information, etc.
  - tableConstraints
```
public TableConstraintsAPI tableConstraints()
```
    Primary key and foreign key constraints encode relationships between fields in tables.
    Primary and foreign keys are informational only and are not enforced. Foreign keys must reference a primary key in another table. This primary key is the parent constraint of the foreign key and the table this primary key is on is the parent table of the foreign key. Similarly, the foreign key is the child constraint of its referenced primary key; the table of the foreign key is the child table of the primary key.
    You can declare primary keys and foreign keys as part of the table specification during table creation. You can also add or drop constraints on existing tables.
  - tables
```
public TablesAPI tables()
```
    A table resides in the third layer of Unity Catalog’s three-level namespace. It contains rows of data. To create a table, users must have CREATE_TABLE and USE_SCHEMA permissions on the schema, and they must have the USE_CATALOG permission on its parent catalog. To query a table, users must have the SELECT permission on the table, and they must have the USE_CATALOG permission on its parent catalog and the USE_SCHEMA permission on its parent schema.
    A table can be managed or external. From an API perspective, a __VIEW__ is a particular kind of table (rather than a managed or external table).
  - tokenManagement
```
public TokenManagementAPI tokenManagement()
```
    Enables administrators to get all tokens and delete tokens for other users. Admins can either get every token, get a specific token by ID, or get all tokens for a particular user.
  - tokens
```
public TokensAPI tokens()
```
    The Token API allows you to create, list, and revoke tokens that can be used to authenticate and access Databricks REST APIs.
  - users
```
public UsersAPI users()
```
    User identities recognized by Databricks and represented by email addresses.
    Databricks recommends using SCIM provisioning to sync users and groups automatically from your identity provider to your Databricks workspace. SCIM streamlines onboarding a new employee or team by using your identity provider to create users and groups in Databricks workspace and give them the proper level of access. When a user leaves your organization or no longer needs access to Databricks workspace, admins can terminate the user in your identity provider and that user’s account will also be removed from Databricks workspace. This ensures a consistent offboarding process and prevents unauthorized users from accessing sensitive data.
  - vectorSearchEndpoints
```
public VectorSearchEndpointsAPI vectorSearchEndpoints()
```
    Endpoint**: Represents the compute resources to host vector search indexes.
  - vectorSearchIndexes
```
public VectorSearchIndexesAPI vectorSearchIndexes()
```
    **Index**: An efficient representation of your embedding vectors that supports real-time and efficient approximate nearest neighbor (ANN) search queries.
    There are 2 types of Vector Search indexes: * **Delta Sync Index**: An index that automatically syncs with a source Delta Table, automatically and incrementally updating the index as the underlying data in the Delta Table changes. * **Direct Vector Access Index**: An index that supports direct read and write of vectors and metadata through our REST and SDK APIs. With this model, the user manages index updates.
  - volumes
```
public VolumesAPI volumes()
```
    Volumes are a Unity Catalog (UC) capability for accessing, storing, governing, organizing and processing files. Use cases include running machine learning on unstructured data such as image, audio, video, or PDF files, organizing data sets during the data exploration stages in data science, working with libraries that require access to the local file system on cluster machines, storing library and config files of arbitrary formats such as .whl or .txt centrally and providing secure access across workspaces to it, or transforming and querying non-tabular data files in ETL.
  - warehouses
```
public WarehousesAPI warehouses()
```
    A SQL warehouse is a compute resource that lets you run SQL commands on data objects within Databricks SQL. Compute resources are infrastructure resources that provide processing capabilities in the cloud.
  - workspace
```
public WorkspaceAPI workspace()
```
    The Workspace API allows you to list, import, export, and delete notebooks and folders.
    A notebook is a web-based interface to a document that contains runnable code, visualizations, and explanatory text.
  - workspaceBindings
```
public WorkspaceBindingsAPI workspaceBindings()
```
    A securable in Databricks can be configured as __OPEN__ or __ISOLATED__. An __OPEN__ securable can be accessed from any workspace, while an __ISOLATED__ securable can only be accessed from a configured list of workspaces. This API allows you to configure (bind) securables to workspaces.
    NOTE: The __isolation_mode__ is configured for the securable itself (using its Update method) and the workspace bindings are only consulted when the securable's __isolation_mode__ is set to __ISOLATED__.
    A securable's workspace bindings can be configured by a metastore admin or the owner of the securable.
    The original path (/api/2.1/unity-catalog/workspace-bindings/catalogs/{name}) is deprecated. Please use the new path (/api/2.1/unity-catalog/bindings/{securable_type}/{securable_name}) which introduces the ability to bind a securable in READ_ONLY mode (catalogs only).
    Securables that support binding: - catalog
  - workspaceConf
```
public WorkspaceConfAPI workspaceConf()
```
    This API allows updating known workspace settings for advanced users.
  - withAccountAccessControlProxyImpl
```
public WorkspaceClient withAccountAccessControlProxyImpl(AccountAccessControlProxyService accountAccessControlProxy)
```
    Replace the default AccountAccessControlProxyService with a custom implementation.
  - withAccountAccessControlProxyAPI
```
public WorkspaceClient withAccountAccessControlProxyAPI(AccountAccessControlProxyAPI accountAccessControlProxy)
```
    Replace the default AccountAccessControlProxyAPI with a custom implementation.
  - withAlertsImpl
```
public WorkspaceClient withAlertsImpl(AlertsService alerts)
```
    Replace the default AlertsService with a custom implementation.
  - withAlertsAPI
```
public WorkspaceClient withAlertsAPI(AlertsAPI alerts)
```
    Replace the default AlertsAPI with a custom implementation.
  - withAppsImpl
```
public WorkspaceClient withAppsImpl(AppsService apps)
```
    Replace the default AppsService with a custom implementation.
  - withAppsAPI
```
public WorkspaceClient withAppsAPI(AppsAPI apps)
```
    Replace the default AppsAPI with a custom implementation.
  - withArtifactAllowlistsImpl
```
public WorkspaceClient withArtifactAllowlistsImpl(ArtifactAllowlistsService artifactAllowlists)
```
    Replace the default ArtifactAllowlistsService with a custom implementation.
  - withArtifactAllowlistsAPI
```
public WorkspaceClient withArtifactAllowlistsAPI(ArtifactAllowlistsAPI artifactAllowlists)
```
    Replace the default ArtifactAllowlistsAPI with a custom implementation.
  - withCatalogsImpl
```
public WorkspaceClient withCatalogsImpl(CatalogsService catalogs)
```
    Replace the default CatalogsService with a custom implementation.
  - withCatalogsAPI
```
public WorkspaceClient withCatalogsAPI(CatalogsAPI catalogs)
```
    Replace the default CatalogsAPI with a custom implementation.
  - withCleanRoomsImpl
```
public WorkspaceClient withCleanRoomsImpl(CleanRoomsService cleanRooms)
```
    Replace the default CleanRoomsService with a custom implementation.
  - withCleanRoomsAPI
```
public WorkspaceClient withCleanRoomsAPI(CleanRoomsAPI cleanRooms)
```
    Replace the default CleanRoomsAPI with a custom implementation.
  - withClusterPoliciesImpl
```
public WorkspaceClient withClusterPoliciesImpl(ClusterPoliciesService clusterPolicies)
```
    Replace the default ClusterPoliciesService with a custom implementation.
  - withClusterPoliciesAPI
```
public WorkspaceClient withClusterPoliciesAPI(ClusterPoliciesAPI clusterPolicies)
```
    Replace the default ClusterPoliciesAPI with a custom implementation.
  - withClustersImpl
```
public WorkspaceClient withClustersImpl(ClustersService clusters)
```
    Replace the default ClustersService with a custom implementation.
  - withClustersAPI
```
public WorkspaceClient withClustersAPI(ClustersExt clusters)
```
    Replace the default ClustersAPI with a custom implementation.
  - withCommandExecutionImpl
```
public WorkspaceClient withCommandExecutionImpl(CommandExecutionService commandExecution)
```
    Replace the default CommandExecutionService with a custom implementation.
  - withCommandExecutionAPI
```
public WorkspaceClient withCommandExecutionAPI(CommandExecutionAPI commandExecution)
```
    Replace the default CommandExecutionAPI with a custom implementation.
  - withConnectionsImpl
```
public WorkspaceClient withConnectionsImpl(ConnectionsService connections)
```
    Replace the default ConnectionsService with a custom implementation.
  - withConnectionsAPI
```
public WorkspaceClient withConnectionsAPI(ConnectionsAPI connections)
```
    Replace the default ConnectionsAPI with a custom implementation.
  - withConsumerFulfillmentsImpl
```
public WorkspaceClient withConsumerFulfillmentsImpl(ConsumerFulfillmentsService consumerFulfillments)
```
    Replace the default ConsumerFulfillmentsService with a custom implementation.
  - withConsumerFulfillmentsAPI
```
public WorkspaceClient withConsumerFulfillmentsAPI(ConsumerFulfillmentsAPI consumerFulfillments)
```
    Replace the default ConsumerFulfillmentsAPI with a custom implementation.
  - withConsumerInstallationsImpl
```
public WorkspaceClient withConsumerInstallationsImpl(ConsumerInstallationsService consumerInstallations)
```
    Replace the default ConsumerInstallationsService with a custom implementation.
  - withConsumerInstallationsAPI
```
public WorkspaceClient withConsumerInstallationsAPI(ConsumerInstallationsAPI consumerInstallations)
```
    Replace the default ConsumerInstallationsAPI with a custom implementation.
  - withConsumerListingsImpl
```
public WorkspaceClient withConsumerListingsImpl(ConsumerListingsService consumerListings)
```
    Replace the default ConsumerListingsService with a custom implementation.
  - withConsumerListingsAPI
```
public WorkspaceClient withConsumerListingsAPI(ConsumerListingsAPI consumerListings)
```
    Replace the default ConsumerListingsAPI with a custom implementation.
  - withConsumerPersonalizationRequestsImpl
```
public WorkspaceClient withConsumerPersonalizationRequestsImpl(ConsumerPersonalizationRequestsService consumerPersonalizationRequests)
```
    Replace the default ConsumerPersonalizationRequestsService with a custom implementation.
  - withConsumerPersonalizationRequestsAPI
```
public WorkspaceClient withConsumerPersonalizationRequestsAPI(ConsumerPersonalizationRequestsAPI consumerPersonalizationRequests)
```
    Replace the default ConsumerPersonalizationRequestsAPI with a custom implementation.
  - withConsumerProvidersImpl
```
public WorkspaceClient withConsumerProvidersImpl(ConsumerProvidersService consumerProviders)
```
    Replace the default ConsumerProvidersService with a custom implementation.
  - withConsumerProvidersAPI
```
public WorkspaceClient withConsumerProvidersAPI(ConsumerProvidersAPI consumerProviders)
```
    Replace the default ConsumerProvidersAPI with a custom implementation.
  - withCredentialsManagerImpl
```
public WorkspaceClient withCredentialsManagerImpl(CredentialsManagerService credentialsManager)
```
    Replace the default CredentialsManagerService with a custom implementation.
  - withCredentialsManagerAPI
```
public WorkspaceClient withCredentialsManagerAPI(CredentialsManagerAPI credentialsManager)
```
    Replace the default CredentialsManagerAPI with a custom implementation.
  - withCurrentUserImpl
```
public WorkspaceClient withCurrentUserImpl(CurrentUserService currentUser)
```
    Replace the default CurrentUserService with a custom implementation.
  - withCurrentUserAPI
```
public WorkspaceClient withCurrentUserAPI(CurrentUserAPI currentUser)
```
    Replace the default CurrentUserAPI with a custom implementation.
  - withDashboardWidgetsImpl
```
public WorkspaceClient withDashboardWidgetsImpl(DashboardWidgetsService dashboardWidgets)
```
    Replace the default DashboardWidgetsService with a custom implementation.
  - withDashboardWidgetsAPI
```
public WorkspaceClient withDashboardWidgetsAPI(DashboardWidgetsAPI dashboardWidgets)
```
    Replace the default DashboardWidgetsAPI with a custom implementation.
  - withDashboardsImpl
```
public WorkspaceClient withDashboardsImpl(DashboardsService dashboards)
```
    Replace the default DashboardsService with a custom implementation.
  - withDashboardsAPI
```
public WorkspaceClient withDashboardsAPI(DashboardsAPI dashboards)
```
    Replace the default DashboardsAPI with a custom implementation.
  - withDataSourcesImpl
```
public WorkspaceClient withDataSourcesImpl(DataSourcesService dataSources)
```
    Replace the default DataSourcesService with a custom implementation.
  - withDataSourcesAPI
```
public WorkspaceClient withDataSourcesAPI(DataSourcesAPI dataSources)
```
    Replace the default DataSourcesAPI with a custom implementation.
  - withDbfsImpl
```
public WorkspaceClient withDbfsImpl(DbfsService dbfs)
```
    Replace the default DbfsService with a custom implementation.
  - withDbfsAPI
```
public WorkspaceClient withDbfsAPI(DbfsExt dbfs)
```
    Replace the default DbfsAPI with a custom implementation.
  - withDbsqlPermissionsImpl
```
public WorkspaceClient withDbsqlPermissionsImpl(DbsqlPermissionsService dbsqlPermissions)
```
    Replace the default DbsqlPermissionsService with a custom implementation.
  - withDbsqlPermissionsAPI
```
public WorkspaceClient withDbsqlPermissionsAPI(DbsqlPermissionsAPI dbsqlPermissions)
```
    Replace the default DbsqlPermissionsAPI with a custom implementation.
  - withExperimentsImpl
```
public WorkspaceClient withExperimentsImpl(ExperimentsService experiments)
```
    Replace the default ExperimentsService with a custom implementation.
  - withExperimentsAPI
```
public WorkspaceClient withExperimentsAPI(ExperimentsAPI experiments)
```
    Replace the default ExperimentsAPI with a custom implementation.
  - withExternalLocationsImpl
```
public WorkspaceClient withExternalLocationsImpl(ExternalLocationsService externalLocations)
```
    Replace the default ExternalLocationsService with a custom implementation.
  - withExternalLocationsAPI
```
public WorkspaceClient withExternalLocationsAPI(ExternalLocationsAPI externalLocations)
```
    Replace the default ExternalLocationsAPI with a custom implementation.
  - withFilesImpl
```
public WorkspaceClient withFilesImpl(FilesService files)
```
    Replace the default FilesService with a custom implementation.
  - withFilesAPI
```
public WorkspaceClient withFilesAPI(FilesAPI files)
```
    Replace the default FilesAPI with a custom implementation.
  - withFunctionsImpl
```
public WorkspaceClient withFunctionsImpl(FunctionsService functions)
```
    Replace the default FunctionsService with a custom implementation.
  - withFunctionsAPI
```
public WorkspaceClient withFunctionsAPI(FunctionsAPI functions)
```
    Replace the default FunctionsAPI with a custom implementation.
  - withGitCredentialsImpl
```
public WorkspaceClient withGitCredentialsImpl(GitCredentialsService gitCredentials)
```
    Replace the default GitCredentialsService with a custom implementation.
  - withGitCredentialsAPI
```
public WorkspaceClient withGitCredentialsAPI(GitCredentialsAPI gitCredentials)
```
    Replace the default GitCredentialsAPI with a custom implementation.
  - withGlobalInitScriptsImpl
```
public WorkspaceClient withGlobalInitScriptsImpl(GlobalInitScriptsService globalInitScripts)
```
    Replace the default GlobalInitScriptsService with a custom implementation.
  - withGlobalInitScriptsAPI
```
public WorkspaceClient withGlobalInitScriptsAPI(GlobalInitScriptsAPI globalInitScripts)
```
    Replace the default GlobalInitScriptsAPI with a custom implementation.
  - withGrantsImpl
```
public WorkspaceClient withGrantsImpl(GrantsService grants)
```
    Replace the default GrantsService with a custom implementation.
  - withGrantsAPI
```
public WorkspaceClient withGrantsAPI(GrantsAPI grants)
```
    Replace the default GrantsAPI with a custom implementation.
  - withGroupsImpl
```
public WorkspaceClient withGroupsImpl(GroupsService groups)
```
    Replace the default GroupsService with a custom implementation.
  - withGroupsAPI
```
public WorkspaceClient withGroupsAPI(GroupsAPI groups)
```
    Replace the default GroupsAPI with a custom implementation.
  - withInstancePoolsImpl
```
public WorkspaceClient withInstancePoolsImpl(InstancePoolsService instancePools)
```
    Replace the default InstancePoolsService with a custom implementation.
  - withInstancePoolsAPI
```
public WorkspaceClient withInstancePoolsAPI(InstancePoolsAPI instancePools)
```
    Replace the default InstancePoolsAPI with a custom implementation.
  - withInstanceProfilesImpl
```
public WorkspaceClient withInstanceProfilesImpl(InstanceProfilesService instanceProfiles)
```
    Replace the default InstanceProfilesService with a custom implementation.
  - withInstanceProfilesAPI
```
public WorkspaceClient withInstanceProfilesAPI(InstanceProfilesAPI instanceProfiles)
```
    Replace the default InstanceProfilesAPI with a custom implementation.
  - withIpAccessListsImpl
```
public WorkspaceClient withIpAccessListsImpl(IpAccessListsService ipAccessLists)
```
    Replace the default IpAccessListsService with a custom implementation.
  - withIpAccessListsAPI
```
public WorkspaceClient withIpAccessListsAPI(IpAccessListsAPI ipAccessLists)
```
    Replace the default IpAccessListsAPI with a custom implementation.
  - withJobsImpl
```
public WorkspaceClient withJobsImpl(JobsService jobs)
```
    Replace the default JobsService with a custom implementation.
  - withJobsAPI
```
public WorkspaceClient withJobsAPI(JobsAPI jobs)
```
    Replace the default JobsAPI with a custom implementation.
  - withLakehouseMonitorsImpl
```
public WorkspaceClient withLakehouseMonitorsImpl(LakehouseMonitorsService lakehouseMonitors)
```
    Replace the default LakehouseMonitorsService with a custom implementation.
  - withLakehouseMonitorsAPI
```
public WorkspaceClient withLakehouseMonitorsAPI(LakehouseMonitorsAPI lakehouseMonitors)
```
    Replace the default LakehouseMonitorsAPI with a custom implementation.
  - withLakeviewImpl
```
public WorkspaceClient withLakeviewImpl(LakeviewService lakeview)
```
    Replace the default LakeviewService with a custom implementation.
  - withLakeviewAPI
```
public WorkspaceClient withLakeviewAPI(LakeviewAPI lakeview)
```
    Replace the default LakeviewAPI with a custom implementation.
  - withLibrariesImpl
```
public WorkspaceClient withLibrariesImpl(LibrariesService libraries)
```
    Replace the default LibrariesService with a custom implementation.
  - withLibrariesAPI
```
public WorkspaceClient withLibrariesAPI(LibrariesAPI libraries)
```
    Replace the default LibrariesAPI with a custom implementation.
  - withMetastoresImpl
```
public WorkspaceClient withMetastoresImpl(MetastoresService metastores)
```
    Replace the default MetastoresService with a custom implementation.
  - withMetastoresAPI
```
public WorkspaceClient withMetastoresAPI(MetastoresAPI metastores)
```
    Replace the default MetastoresAPI with a custom implementation.
  - withModelRegistryImpl
```
public WorkspaceClient withModelRegistryImpl(ModelRegistryService modelRegistry)
```
    Replace the default ModelRegistryService with a custom implementation.
  - withModelRegistryAPI
```
public WorkspaceClient withModelRegistryAPI(ModelRegistryAPI modelRegistry)
```
    Replace the default ModelRegistryAPI with a custom implementation.
  - withModelVersionsImpl
```
public WorkspaceClient withModelVersionsImpl(ModelVersionsService modelVersions)
```
    Replace the default ModelVersionsService with a custom implementation.
  - withModelVersionsAPI
```
public WorkspaceClient withModelVersionsAPI(ModelVersionsAPI modelVersions)
```
    Replace the default ModelVersionsAPI with a custom implementation.
  - withOnlineTablesImpl
```
public WorkspaceClient withOnlineTablesImpl(OnlineTablesService onlineTables)
```
    Replace the default OnlineTablesService with a custom implementation.
  - withOnlineTablesAPI
```
public WorkspaceClient withOnlineTablesAPI(OnlineTablesAPI onlineTables)
```
    Replace the default OnlineTablesAPI with a custom implementation.
  - withPermissionMigrationImpl
```
public WorkspaceClient withPermissionMigrationImpl(PermissionMigrationService permissionMigration)
```
    Replace the default PermissionMigrationService with a custom implementation.
  - withPermissionMigrationAPI
```
public WorkspaceClient withPermissionMigrationAPI(PermissionMigrationAPI permissionMigration)
```
    Replace the default PermissionMigrationAPI with a custom implementation.
  - withPermissionsImpl
```
public WorkspaceClient withPermissionsImpl(PermissionsService permissions)
```
    Replace the default PermissionsService with a custom implementation.
  - withPermissionsAPI
```
public WorkspaceClient withPermissionsAPI(PermissionsAPI permissions)
```
    Replace the default PermissionsAPI with a custom implementation.
  - withPipelinesImpl
```
public WorkspaceClient withPipelinesImpl(PipelinesService pipelines)
```
    Replace the default PipelinesService with a custom implementation.
  - withPipelinesAPI
```
public WorkspaceClient withPipelinesAPI(PipelinesAPI pipelines)
```
    Replace the default PipelinesAPI with a custom implementation.
  - withPolicyFamiliesImpl
```
public WorkspaceClient withPolicyFamiliesImpl(PolicyFamiliesService policyFamilies)
```
    Replace the default PolicyFamiliesService with a custom implementation.
  - withPolicyFamiliesAPI
```
public WorkspaceClient withPolicyFamiliesAPI(PolicyFamiliesAPI policyFamilies)
```
    Replace the default PolicyFamiliesAPI with a custom implementation.
  - withProviderExchangeFiltersImpl
```
public WorkspaceClient withProviderExchangeFiltersImpl(ProviderExchangeFiltersService providerExchangeFilters)
```
    Replace the default ProviderExchangeFiltersService with a custom implementation.
  - withProviderExchangeFiltersAPI
```
public WorkspaceClient withProviderExchangeFiltersAPI(ProviderExchangeFiltersAPI providerExchangeFilters)
```
    Replace the default ProviderExchangeFiltersAPI with a custom implementation.
  - withProviderExchangesImpl
```
public WorkspaceClient withProviderExchangesImpl(ProviderExchangesService providerExchanges)
```
    Replace the default ProviderExchangesService with a custom implementation.
  - withProviderExchangesAPI
```
public WorkspaceClient withProviderExchangesAPI(ProviderExchangesAPI providerExchanges)
```
    Replace the default ProviderExchangesAPI with a custom implementation.
  - withProviderFilesImpl
```
public WorkspaceClient withProviderFilesImpl(ProviderFilesService providerFiles)
```
    Replace the default ProviderFilesService with a custom implementation.
  - withProviderFilesAPI
```
public WorkspaceClient withProviderFilesAPI(ProviderFilesAPI providerFiles)
```
    Replace the default ProviderFilesAPI with a custom implementation.
  - withProviderListingsImpl
```
public WorkspaceClient withProviderListingsImpl(ProviderListingsService providerListings)
```
    Replace the default ProviderListingsService with a custom implementation.
  - withProviderListingsAPI
```
public WorkspaceClient withProviderListingsAPI(ProviderListingsAPI providerListings)
```
    Replace the default ProviderListingsAPI with a custom implementation.
  - withProviderPersonalizationRequestsImpl
```
public WorkspaceClient withProviderPersonalizationRequestsImpl(ProviderPersonalizationRequestsService providerPersonalizationRequests)
```
    Replace the default ProviderPersonalizationRequestsService with a custom implementation.
  - withProviderPersonalizationRequestsAPI
```
public WorkspaceClient withProviderPersonalizationRequestsAPI(ProviderPersonalizationRequestsAPI providerPersonalizationRequests)
```
    Replace the default ProviderPersonalizationRequestsAPI with a custom implementation.
  - withProviderProviderAnalyticsDashboardsImpl
```
public WorkspaceClient withProviderProviderAnalyticsDashboardsImpl(ProviderProviderAnalyticsDashboardsService providerProviderAnalyticsDashboards)
```
    Replace the default ProviderProviderAnalyticsDashboardsService with a custom implementation.
  - withProviderProviderAnalyticsDashboardsAPI
```
public WorkspaceClient withProviderProviderAnalyticsDashboardsAPI(ProviderProviderAnalyticsDashboardsAPI providerProviderAnalyticsDashboards)
```
    Replace the default ProviderProviderAnalyticsDashboardsAPI with a custom implementation.
  - withProviderProvidersImpl
```
public WorkspaceClient withProviderProvidersImpl(ProviderProvidersService providerProviders)
```
    Replace the default ProviderProvidersService with a custom implementation.
  - withProviderProvidersAPI
```
public WorkspaceClient withProviderProvidersAPI(ProviderProvidersAPI providerProviders)
```
    Replace the default ProviderProvidersAPI with a custom implementation.
  - withProvidersImpl
```
public WorkspaceClient withProvidersImpl(ProvidersService providers)
```
    Replace the default ProvidersService with a custom implementation.
  - withProvidersAPI
```
public WorkspaceClient withProvidersAPI(ProvidersAPI providers)
```
    Replace the default ProvidersAPI with a custom implementation.
  - withQueriesImpl
```
public WorkspaceClient withQueriesImpl(QueriesService queries)
```
    Replace the default QueriesService with a custom implementation.
  - withQueriesAPI
```
public WorkspaceClient withQueriesAPI(QueriesAPI queries)
```
    Replace the default QueriesAPI with a custom implementation.
  - withQueryHistoryImpl
```
public WorkspaceClient withQueryHistoryImpl(QueryHistoryService queryHistory)
```
    Replace the default QueryHistoryService with a custom implementation.
  - withQueryHistoryAPI
```
public WorkspaceClient withQueryHistoryAPI(QueryHistoryAPI queryHistory)
```
    Replace the default QueryHistoryAPI with a custom implementation.
  - withQueryVisualizationsImpl
```
public WorkspaceClient withQueryVisualizationsImpl(QueryVisualizationsService queryVisualizations)
```
    Replace the default QueryVisualizationsService with a custom implementation.
  - withQueryVisualizationsAPI
```
public WorkspaceClient withQueryVisualizationsAPI(QueryVisualizationsAPI queryVisualizations)
```
    Replace the default QueryVisualizationsAPI with a custom implementation.
  - withRecipientActivationImpl
```
public WorkspaceClient withRecipientActivationImpl(RecipientActivationService recipientActivation)
```
    Replace the default RecipientActivationService with a custom implementation.
  - withRecipientActivationAPI
```
public WorkspaceClient withRecipientActivationAPI(RecipientActivationAPI recipientActivation)
```
    Replace the default RecipientActivationAPI with a custom implementation.
  - withRecipientsImpl
```
public WorkspaceClient withRecipientsImpl(RecipientsService recipients)
```
    Replace the default RecipientsService with a custom implementation.
  - withRecipientsAPI
```
public WorkspaceClient withRecipientsAPI(RecipientsAPI recipients)
```
    Replace the default RecipientsAPI with a custom implementation.
  - withRegisteredModelsImpl
```
public WorkspaceClient withRegisteredModelsImpl(RegisteredModelsService registeredModels)
```
    Replace the default RegisteredModelsService with a custom implementation.
  - withRegisteredModelsAPI
```
public WorkspaceClient withRegisteredModelsAPI(RegisteredModelsAPI registeredModels)
```
    Replace the default RegisteredModelsAPI with a custom implementation.
  - withReposImpl
```
public WorkspaceClient withReposImpl(ReposService repos)
```
    Replace the default ReposService with a custom implementation.
  - withReposAPI
```
public WorkspaceClient withReposAPI(ReposAPI repos)
```
    Replace the default ReposAPI with a custom implementation.
  - withSchemasImpl
```
public WorkspaceClient withSchemasImpl(SchemasService schemas)
```
    Replace the default SchemasService with a custom implementation.
  - withSchemasAPI
```
public WorkspaceClient withSchemasAPI(SchemasAPI schemas)
```
    Replace the default SchemasAPI with a custom implementation.
  - withSecretsImpl
```
public WorkspaceClient withSecretsImpl(SecretsService secrets)
```
    Replace the default SecretsService with a custom implementation.
  - withSecretsAPI
```
public WorkspaceClient withSecretsAPI(SecretsExt secrets)
```
    Replace the default SecretsAPI with a custom implementation.
  - withServicePrincipalsImpl
```
public WorkspaceClient withServicePrincipalsImpl(ServicePrincipalsService servicePrincipals)
```
    Replace the default ServicePrincipalsService with a custom implementation.
  - withServicePrincipalsAPI
```
public WorkspaceClient withServicePrincipalsAPI(ServicePrincipalsAPI servicePrincipals)
```
    Replace the default ServicePrincipalsAPI with a custom implementation.
  - withServingEndpointsImpl
```
public WorkspaceClient withServingEndpointsImpl(ServingEndpointsService servingEndpoints)
```
    Replace the default ServingEndpointsService with a custom implementation.
  - withServingEndpointsAPI
```
public WorkspaceClient withServingEndpointsAPI(ServingEndpointsAPI servingEndpoints)
```
    Replace the default ServingEndpointsAPI with a custom implementation.
  - withSettingsImpl
```
public WorkspaceClient withSettingsImpl(SettingsService settings)
```
    Replace the default SettingsService with a custom implementation.
  - withSettingsAPI
```
public WorkspaceClient withSettingsAPI(SettingsAPI settings)
```
    Replace the default SettingsAPI with a custom implementation.
  - withSharesImpl
```
public WorkspaceClient withSharesImpl(SharesService shares)
```
    Replace the default SharesService with a custom implementation.
  - withSharesAPI
```
public WorkspaceClient withSharesAPI(SharesAPI shares)
```
    Replace the default SharesAPI with a custom implementation.
  - withStatementExecutionImpl
```
public WorkspaceClient withStatementExecutionImpl(StatementExecutionService statementExecution)
```
    Replace the default StatementExecutionService with a custom implementation.
  - withStatementExecutionAPI
```
public WorkspaceClient withStatementExecutionAPI(StatementExecutionAPI statementExecution)
```
    Replace the default StatementExecutionAPI with a custom implementation.
  - withStorageCredentialsImpl
```
public WorkspaceClient withStorageCredentialsImpl(StorageCredentialsService storageCredentials)
```
    Replace the default StorageCredentialsService with a custom implementation.
  - withStorageCredentialsAPI
```
public WorkspaceClient withStorageCredentialsAPI(StorageCredentialsAPI storageCredentials)
```
    Replace the default StorageCredentialsAPI with a custom implementation.
  - withSystemSchemasImpl
```
public WorkspaceClient withSystemSchemasImpl(SystemSchemasService systemSchemas)
```
    Replace the default SystemSchemasService with a custom implementation.
  - withSystemSchemasAPI
```
public WorkspaceClient withSystemSchemasAPI(SystemSchemasAPI systemSchemas)
```
    Replace the default SystemSchemasAPI with a custom implementation.
  - withTableConstraintsImpl
```
public WorkspaceClient withTableConstraintsImpl(TableConstraintsService tableConstraints)
```
    Replace the default TableConstraintsService with a custom implementation.
  - withTableConstraintsAPI
```
public WorkspaceClient withTableConstraintsAPI(TableConstraintsAPI tableConstraints)
```
    Replace the default TableConstraintsAPI with a custom implementation.
  - withTablesImpl
```
public WorkspaceClient withTablesImpl(TablesService tables)
```
    Replace the default TablesService with a custom implementation.
  - withTablesAPI
```
public WorkspaceClient withTablesAPI(TablesAPI tables)
```
    Replace the default TablesAPI with a custom implementation.
  - withTokenManagementImpl
```
public WorkspaceClient withTokenManagementImpl(TokenManagementService tokenManagement)
```
    Replace the default TokenManagementService with a custom implementation.
  - withTokenManagementAPI
```
public WorkspaceClient withTokenManagementAPI(TokenManagementAPI tokenManagement)
```
    Replace the default TokenManagementAPI with a custom implementation.
  - withTokensImpl
```
public WorkspaceClient withTokensImpl(TokensService tokens)
```
    Replace the default TokensService with a custom implementation.
  - withTokensAPI
```
public WorkspaceClient withTokensAPI(TokensAPI tokens)
```
    Replace the default TokensAPI with a custom implementation.
  - withUsersImpl
```
public WorkspaceClient withUsersImpl(UsersService users)
```
    Replace the default UsersService with a custom implementation.
  - withUsersAPI
```
public WorkspaceClient withUsersAPI(UsersAPI users)
```
    Replace the default UsersAPI with a custom implementation.
  - withVectorSearchEndpointsImpl
```
public WorkspaceClient withVectorSearchEndpointsImpl(VectorSearchEndpointsService vectorSearchEndpoints)
```
    Replace the default VectorSearchEndpointsService with a custom implementation.
  - withVectorSearchEndpointsAPI
```
public WorkspaceClient withVectorSearchEndpointsAPI(VectorSearchEndpointsAPI vectorSearchEndpoints)
```
    Replace the default VectorSearchEndpointsAPI with a custom implementation.
  - withVectorSearchIndexesImpl
```
public WorkspaceClient withVectorSearchIndexesImpl(VectorSearchIndexesService vectorSearchIndexes)
```
    Replace the default VectorSearchIndexesService with a custom implementation.
  - withVectorSearchIndexesAPI
```
public WorkspaceClient withVectorSearchIndexesAPI(VectorSearchIndexesAPI vectorSearchIndexes)
```
    Replace the default VectorSearchIndexesAPI with a custom implementation.
  - withVolumesImpl
```
public WorkspaceClient withVolumesImpl(VolumesService volumes)
```
    Replace the default VolumesService with a custom implementation.
  - withVolumesAPI
```
public WorkspaceClient withVolumesAPI(VolumesAPI volumes)
```
    Replace the default VolumesAPI with a custom implementation.
  - withWarehousesImpl
```
public WorkspaceClient withWarehousesImpl(WarehousesService warehouses)
```
    Replace the default WarehousesService with a custom implementation.
  - withWarehousesAPI
```
public WorkspaceClient withWarehousesAPI(WarehousesAPI warehouses)
```
    Replace the default WarehousesAPI with a custom implementation.
  - withWorkspaceImpl
```
public WorkspaceClient withWorkspaceImpl(WorkspaceService workspace)
```
    Replace the default WorkspaceService with a custom implementation.
  - withWorkspaceAPI
```
public WorkspaceClient withWorkspaceAPI(WorkspaceAPI workspace)
```
    Replace the default WorkspaceAPI with a custom implementation.
  - withWorkspaceBindingsImpl
```
public WorkspaceClient withWorkspaceBindingsImpl(WorkspaceBindingsService workspaceBindings)
```
    Replace the default WorkspaceBindingsService with a custom implementation.
  - withWorkspaceBindingsAPI
```
public WorkspaceClient withWorkspaceBindingsAPI(WorkspaceBindingsAPI workspaceBindings)
```
    Replace the default WorkspaceBindingsAPI with a custom implementation.
  - withWorkspaceConfImpl
```
public WorkspaceClient withWorkspaceConfImpl(WorkspaceConfService workspaceConf)
```
    Replace the default WorkspaceConfService with a custom implementation.
  - withWorkspaceConfAPI
```
public WorkspaceClient withWorkspaceConfAPI(WorkspaceConfAPI workspaceConf)
```
    Replace the default WorkspaceConfAPI with a custom implementation.
  - apiClient
```
public ApiClient apiClient()
```
  - config
```
public DatabricksConfig config()
```

Class WorkspaceClient

Constructor Summary

Method Summary

Methods inherited from class java.lang.Object

Constructor Detail

WorkspaceClient

WorkspaceClient

WorkspaceClient

WorkspaceClient

Method Detail

accountAccessControlProxy

alerts

apps

artifactAllowlists

catalogs

cleanRooms

clusterPolicies

clusters

commandExecution

connections

consumerFulfillments

consumerInstallations

consumerListings

consumerPersonalizationRequests

consumerProviders

credentialsManager

currentUser

dashboardWidgets

dashboards

dataSources

dbfs

dbsqlPermissions

experiments

externalLocations

files

functions

gitCredentials

globalInitScripts

grants

groups

instancePools

instanceProfiles

ipAccessLists

jobs

lakehouseMonitors

lakeview

libraries

metastores

modelRegistry

modelVersions

onlineTables

permissionMigration

permissions

pipelines

policyFamilies

providerExchangeFilters

providerExchanges

providerFiles

providerListings

providerPersonalizationRequests

providerProviderAnalyticsDashboards

providerProviders

providers

queries

queryHistory

queryVisualizations

recipientActivation

recipients

registeredModels

repos

schemas

secrets

servicePrincipals

servingEndpoints

settings

shares

statementExecution

storageCredentials

systemSchemas

tableConstraints