-
Notifications
You must be signed in to change notification settings - Fork 80
docs: Restructure BladeBridge configuration guide with practical UC namespace example #2135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2135 +/- ##
=======================================
Coverage 63.56% 63.56%
=======================================
Files 100 100
Lines 8503 8503
Branches 885 885
=======================================
Hits 5405 5405
Misses 2931 2931
Partials 167 167 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
✅ 51/51 passed, 10 flaky, 4m36s total Flaky tests:
Running from acceptance #3152 |
gueniai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BesikiML I think this should be part of the "Creating the custom configuration file" section, we can simply state the business intent as an example.
For example:
"So let's say you want to rename your tables or ensure they follow the UC three level namespace paradigm, you can do it as follows:"
and you add everything you have here
…-catalog-in-the-config
Done |
Summary
Improves the BladeBridge configuration documentation by integrating a practical example into the "Creating the custom configuration file" section, making it more actionable and easier to follow.
Changes Made
Documentation Restructuring
Content Improvements
inherit_from,target_sql_file_header, andline_substusage in contextLinked issues
Implemented: https://github.com/databrickslabs/bladerunner/issues/619
Rationale
Previously, the SQL configuration example appeared as a separate section later in the document, disconnected from the setup instructions. This restructuring:
Impact
Testing