databrickslabs / databrickslabs/ontos
[Feature]: Allow deploying to Git repo only
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 212
- Forks
- 71
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 43
Description
Is there an existing issue for this?
- I have searched the existing issues
Problem statement
Instead of deploying to UC only, we should also be able to push to the Git repo, which then can trigger actions.
Proposed Solution
We have to support automation, like Terraform based templating, triggered by Git repo pushes (PR approvals handled on the Git side as needed). In the app role or global settings (as a default), it should be configurable what "Deploy" of a contract or product does. It may create the assets in UC and/or a Git repo.
Additional Context
No response
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
No files, tests, or entry points are identified in the issue. First map the existing Deploy flow and its app-role or global settings, then determine how Git repository pushes, optional Unity Catalog creation, and Terraform-based automation should be configured and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python, terraform
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100