databrickslabs / databrickslabs/ontos
[Feature]: Estate: Instance Identity in Settings
Open
Nobody has claimed this yet.
type/feature
- Dominant language
- Python
- Stars
- 212
- Forks
- 71
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 43
Description
Parent PRD
#143
What to build
Add ONTOS_INSTANCE_ID and ONTOS_INSTANCE_NAME to the application settings, configurable via the Settings UI. These fields identify the local Ontos instance for federation purposes.
- Add fields to the
Settingsmodel inconfig.pywith defaults derived fromDATABRICKS_WORKSPACE_ID+DATABRICKS_APP_NAME - Expose in the Settings UI so admins can override the defaults
- The instance ID is stamped on all exported entities in subsequent slices
See "Instance Identity" section of the parent PRD for full details.
Acceptance criteria
-
ONTOS_INSTANCE_IDandONTOS_INSTANCE_NAMEfields exist in Settings model - Defaults are derived from
DATABRICKS_WORKSPACE_ID+DATABRICKS_APP_NAMEwhen not explicitly set - Settings UI shows instance identity fields and allows editing
- Instance identity values are accessible via
get_settings()throughout the app
Blocked by
None - can start immediately
User stories addressed
- User story 1
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 the Settings model in config.py, then locate the Settings UI and get_settings() callers. Implement the two identity fields, their derived defaults and editable UI values, and verify that get_settings() exposes the configured values throughout the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100