-
Notifications
You must be signed in to change notification settings - Fork 109
direct: Add dashboards support #3725
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
Open
shreyas-goenka
wants to merge
100
commits into
main
Choose a base branch
from
direct/dashboard
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 13, 2025
## Why Used in #3725 to provide local test coverage. ## Tests Existing tests pass with slight modifications.
40 failing tests:
|
…ange This merge incorporates changes from PR #3741 which adds an isLocal parameter to FieldTriggers and ClassifyChange methods to differentiate between local changes (user modifications) and remote changes (drift detection). Key changes: - Renamed ActionTypeUnset to ActionTypeUndefined - Updated FieldTriggers to accept isLocal bool parameter - Updated ClassifyChange to accept isLocal bool parameter - Consolidated dashboard's separate FieldTriggersLocal/Remote methods into single FieldTriggers(isLocal bool) method - Updated adapter to store separate trigger maps for local and remote 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Resolved conflicts: - bundle/direct/dresources/adapter.go: Merged documentation for FieldTriggers method, combining detailed explanation from HEAD with note about initialization timing from main - acceptance/bundle/resources/dashboards/test.toml: Kept HEAD version with proper warehouse requirements and etag replacements for new dashboard tests
denik
approved these changes
Oct 29, 2025
...ce/bundle/resources/dashboards/publish-failure-cleans-up-dashboard/out.dashboardrequests.txt
Show resolved
Hide resolved
acceptance/bundle/resources/dashboards/publish-failure-cleans-up-dashboard/script
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for Databricks Lakeview Dashboards in the direct deployment mode (
DATABRICKS_BUNDLE_ENGINE=direct-exp). Dashboards can now be deployed, updated, and deleted directly via API calls without using Terraform.Key Features
1. Full Dashboard Lifecycle Management
2. Smart Field Change Detection
The implementation uses
FieldTriggersto determine the correct action for each field change:Update Actions (in-place modifications):
display_name- Dashboard name changeswarehouse_id- SQL warehouse assignment changesembed_credentials- Credential embedding toggleserialized_dashboard- Dashboard content/layout changesRecreate Actions (delete + create):
parent_path- Moving dashboard to different folder requires recreationSkip Actions (ignored for diff):
dashboard_id,path,create_time,update_time,lifecycle_stateetag- Skipped for local changes (user edits), but triggers updates for remote drift detectionserialized_dashboard- Skipped for remote drift (etag is sufficient)3. Advanced Capabilities
Parallel API Calls: Refresh operations fetch both draft and published dashboard states concurrently using goroutines for better performance.
Automatic Parent Directory Creation: If the parent directory doesn't exist, it's automatically created before dashboard creation.
Idempotent Delete: Handles already-trashed dashboards gracefully by checking the dashboard state on 403 errors.
embed_credentials Edge Case: Unlike Terraform, this implementation properly detects changes to the
embed_credentialsfield by fetching published dashboard state separately.Serialized Dashboard Flexibility: Supports both string and map/object formats for
serialized_dashboardin bundle configuration.4. Comprehensive Test Coverage
Added 5 new acceptance test suites testing field change behavior:
change-name- Tests display_name updateschange-warehouse-id- Tests warehouse assignment updateschange-embed-credentials- Tests credential embedding togglechange-serialized-dashboard- Tests dashboard content updateschange-parent-path- Tests parent path changes trigger recreateEach test verifies:
Testing
Existing and new unit and integration tests.