the sys.path approach won’t fix this for Lakeflow Connect pipelines. During a dry run, Databricks imports databricks.labs.community_connector before your ingest notebook runs, using only the pipeline’s Environment dependencies.
Fix: Pipeline Settings...
The connector_spec.yaml isn't what controls the UI for custom connectors. When you use the "Add Custom Community Connector" path in the workspace UI, Databricks shows a generic connection form with all available auth types. That form is the same for ...
That error ("is not supported for account") means your Databricks account hasn't been enrolled in the private preview for NCC private endpoints. The feature is currently in private preview, so even if you follow the documentation steps correctly, the...
Yes, this is a bug in the Account Console UI. You've already diagnosed it correctly: for a system-assigned managed identity, managed_identity_id should be omitted entirely from the request payload. An empty string "" is not the same as omitting the f...
That 403 with "rate limit of 0" isn't something you accidentally configured, it's a Databricks-imposed gate that applies to newly created accounts. Even with active trial credit and a valid payment method on file, Foundation Model API access gets hel...
