Describe the issue
When setting up a Lakebase autoscaling project via postgres_projects, a primary endpoint comes predefined which is counter to the example in the documentation.
If we follow the example, we get a conflict "read_write endpoint already exists".
That is, it's not actually possible to configure the primary endpoint because it's already defined implicitly.
Configuration
Use the example linked above.
Steps to reproduce the behavior
- Run
databricks bundle deploy ...
- Run
databricks bundle run ...
- See error
Expected Behavior
Clear and concise description of what should have happened
Actual Behavior
Clear and concise description of what actually happened
OS and CLI version
Please provide the version of the CLI (eg: v0.1.2) and the operating system (eg: windows). You can run databricks --version to get the version of your Databricks CLI
Is this a regression?
Did this work in a previous version of the CLI? If so, which versions did you try?
Debug Logs
Output logs if you run the command with debug logs enabled. Example: databricks bundle deploy --log-level=debug. Redact if needed
Describe the issue
When setting up a Lakebase autoscaling project via
postgres_projects, aprimaryendpoint comes predefined which is counter to the example in the documentation.If we follow the example, we get a conflict "read_write endpoint already exists".
That is, it's not actually possible to configure the primary endpoint because it's already defined implicitly.
Configuration
Use the example linked above.
Steps to reproduce the behavior
databricks bundle deploy ...databricks bundle run ...Expected Behavior
Clear and concise description of what should have happened
Actual Behavior
Clear and concise description of what actually happened
OS and CLI version
Please provide the version of the CLI (eg: v0.1.2) and the operating system (eg: windows). You can run databricks --version to get the version of your Databricks CLI
Is this a regression?
Did this work in a previous version of the CLI? If so, which versions did you try?
Debug Logs
Output logs if you run the command with debug logs enabled. Example: databricks bundle deploy --log-level=debug. Redact if needed