Hi @Hertz, Youโre correct that the editEndpoint/editWarehouse
and deleteEndpoint/deleteWarehouse
actions include both the warehouse_id
and warehouse_name
. However, the createWarehouse/createEndpoint
actions do not include the warehouse_id
1.
To get the warehouse names and IDs without creating a bearer token for each account, you could consider the following approach:
-
Use the Databricks REST API: The Databricks REST API provides an endpoint to get the information for...1. You can use the GET /api/2.0/sql/warehouses/{id}
endpoint to get the information for a single SQL warehouse, including its unique identifier (ID) and logical name (name). However, this would still require authentication.
-
Create a Warehouse Metadata Table: Another workaround is to set up a Databricks job or notebook that periodically queries the system tables to retrieve warehouse information (including names and IDs). You can store this information in a separate table (e.g., a dedicated โWarehouse Metadataโ table) wi...2. This approach would not require creating a bearer token for each account.
Please note that these methods still require some form of authentication to access the Databricks API or the Databricks workspace. If you have many accounts, you might want to consider using a centralized identity management system to manage the tokens. This could simplify the process of managing multiple tokens and reduce the overhead of authentication.
I hope this helps! If you have any other questions, feel free to ask. ๐