Question regarding Databricks Apps deployment

[Khasim_1]

Hello Databricks Community,

I am currently working on setting up a Databricks App and ran into a few questions.

Here are the details of what I am working with:

• Target Framework: [e.g., Streamlit / Dash]
• Goal: [Briefly describe what you are trying to achieve]
• Current Challenge: [Briefly describe the blocker, e.g., authentication, Unity Catalog connection, etc.]

Has anyone tackled a similar setup?

Any pointers, code snippets, or best practices would be greatly appreciated!

[data_pulse]

@Khasim_1 

When I was developing a Flask-based Databricks App, which integrated Databricks Model Serving, a custom tool-calling agent, and Unity Catalog system tables, I found a few key areas worth considering during setup.

• Application startup: verify app.yaml dependencies, startup command and port configuration.
• Authentication and permissions: Check which identity the app uses and whether it has access to the required Databricks resources.
• Unity Catalog access: Confirm the necessary catalog/schema/table privileges.
• Resource dependencies: Ensure any SQL warehouses or serving endpoints are correctly configured and accessible.
• Troubleshooting: Deployment/runtime logs to distinguish startup errors from resource-access failures.

In my implementation, the App successfully queried job, billing and query metrics and integrated them with an AI agent, so this architecture is workable.

Could you share your framework (Streamlit, Dash or Flask), what you're trying to build, and the specific error or blocker? That would help to contribute further.