databrickslabs / databrickslabs/ontos
[Bug]: Clean up app.yaml entry point and env vars
Open
Beginner friendly
Nobody has claimed this yet.
type/bug
- Dominant language
- Python
- Stars
- 212
- Forks
- 71
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 43
Description
Parent PRD
#188
What to build
Clean up src/app.yaml to be the authoritative runtime config:
- Remove dead env var: Delete
FRONTEND_STATIC_DIR— the backend hardcodesPath(__file__).parent.parent / "static"inapp.pyline 103 and never reads this env var. - Add missing env vars: Add
DATABRICKS_CATALOGandDATABRICKS_SCHEMAwith sensible defaults (e.g.,app_dataandapp_ontos). These are required byconfig.pylines 54-55 and were previously only set via the bundle'sapp_configoverride (which is being removed in the sibling issue). - Verify entry point: Confirm
python backend/src/app.pyworks correctly as the production command (it uses theif __name__block at line 411 which callsuvicorn.run()).
Acceptance criteria
-
FRONTEND_STATIC_DIRenv var removed fromapp.yaml -
DATABRICKS_CATALOGenv var added with default value -
DATABRICKS_SCHEMAenv var added with default value - Entry point
python backend/src/app.pyverified working - No references to
FRONTEND_STATIC_DIRremain in any config file
Blocked by
None - can start immediately
User stories addressed
- User story 7:
app.yamlas single source of truth for runtime configuration - User story 13: Dead configuration removed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/app.yaml, then compare its environment variables with the references in config.py lines 54-55 and the hardcoded static path in app.py line 103. Run python backend/src/app.py and verify the app.yaml changes, entry point, and absence of FRONTEND_STATIC_DIR from configuration files meet the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100