databricks-lakebase-provisioned

Provision and manage Lakebase PostgreSQL databases with OAuth token authentication.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher --skill databricks-lakebase-provisioned-jingyiwng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: databricks-lakebase-provisioned
Source: https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher/tree/main/.claude/skills/databricks-lakebase-provisioned
Command: npx skills add https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher --skill databricks-lakebase-provisioned-jingyiwng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Databricks Lakebase Provisioned databases, handling OAuth token generation, and integrating PostgreSQL with Databricks apps can be complex and error‑prone.

Core Features & Use Cases

  • Provisioning: Create, update, start, stop, and delete Lakebase instances programmatically.
  • Secure Access: Generate short‑lived OAuth tokens for PostgreSQL connections, with refresh logic for production workloads.
  • Integration: Connect Databricks notebooks, apps, and LangChain agents to Lakebase; set up reverse‑ETL synced tables; register instances in Unity Catalog.
  • Typical Scenarios: Building transactional services, persisting agent memory, implementing reverse ETL, or adding a persistent PostgreSQL backend to Databricks Apps.

Quick Start

Use the skill to create a Lakebase instance named “my‑lakebase‑instance”, generate an OAuth token, and connect via psycopg in a single workflow.

Frequently Asked Questions about databricks-lakebase-provisioned

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision and manage a Lakebase PostgreSQL database for OLTP workloads?

To provision Lakebase PostgreSQL for OLTP workloads, use this skill to programmatically create, update, start, stop, and delete Lakebase instances, generating OAuth tokens for secure connections. It manages the full lifecycle of your transactional database instances.

How does OAuth token generation work for connecting to PostgreSQL via psycopg and SQLAlchemy?

OAuth token generation for PostgreSQL connections creates short-lived tokens with built-in refresh logic for production workloads. psycopg3 and SQLAlchemy use these tokens to handle token-based authentication and establish secure SSL connections to the Lakebase instance.

Can I use Databricks Lakebase for reverse ETL and syncing tables to Unity Catalog?

Yes, you can use Databricks Lakebase for reverse ETL by setting up synced tables and registering instances in Unity Catalog. This enables seamless integration between your OLTP PostgreSQL backend and Databricks notebooks or apps.

Do I need the Databricks SDK for Python to set up Lakebase instances?

Yes, you need the Databricks SDK for Python version 0.81.0 or higher, along with psycopg3 and SQLAlchemy, to provision Lakebase instances and handle OAuth token-based authentication and secure SSL connections.

What is the best way to persist LangChain agent memory using a PostgreSQL backend?

The best way to persist LangChain agent memory is to connect your agents to a provisioned Lakebase PostgreSQL instance. This skill generates OAuth tokens and configures secure connections, providing a reliable persistent backend for agent state.

Why does my Lakebase PostgreSQL connection fail when using short-lived OAuth tokens?

Lakebase PostgreSQL connections using short-lived OAuth tokens fail when the token expires without refresh logic. This skill implements automatic token refresh for production workloads, ensuring persistent secure SSL connections via psycopg3 and SQLAlchemy.