-
Notifications
You must be signed in to change notification settings - Fork 121
Add support for alerts to DABs #4004
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
Merged
Merged
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
Collaborator
|
Commit: caa845e
9 interesting tests: 7 KNOWN, 2 SKIP
Top 20 slowest tests (at least 2 minutes):
|
denik
approved these changes
Dec 3, 2025
Collaborator
|
Commit: a6fbd57
41 interesting tests: 19 FAIL, 11 flaky, 7 KNOWN, 3 RECOVERED, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging bot
added a commit
that referenced
this pull request
Dec 4, 2025
## Release v0.279.0 ### Notable Changes * New deployment engine for DABs that does not require Terraform is available to try in experimental mode. Not recommended for production workloads yet. Documentation at [docs/direct.md](docs/direct.md). ### CLI * Introduce `databricks apps logs` command to tail app logs from the CLI ([#3908](#3908)) ### Bundles * Add support for alerts to DABs ([#4004](#4004)) * Allow `file://` URIs in job libraries to reference runtime filesystem paths (e.g., JARs pre-installed on clusters via init scripts). These paths are no longer treated as local files to upload. ([#3884](#3884)) * Pipeline catalog changes now trigger in-place updates instead of recreation (Terraform provider v1.98.0 behavior change) ([#4082](#4082)) ### Dependency updates * Bump Terraform provider to v1.98.0 ([#4082](#4082))
pietern
added a commit
that referenced
this pull request
Dec 5, 2025
## Changes Filter out enum values with DEVELOPMENT or PRIVATE_PREVIEW launch stages when extracting annotations from the OpenAPI spec. Only values with GA, PUBLIC_PREVIEW, or PUBLIC_BETA stages are included in the generated schema. ## Why Different OpenAPI spec versions have inconsistent visibility filtering, causing enum values like LIQUID to appear and disappear across commits. This made the annotations file non-deterministic depending on which spec was used. Evidence of flip-flopping (newest to oldest): - a6fbd57 Add support for alerts to DABs (#4004) - LIQUID re-added - ecc9d54 Regenerate autogenerated files (#3981) - LIQUID removed - 89b2786 Upgrade go sdk to 0.85.0 (#3769) - LIQUID first added
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.
Changes
Support for alerts was removed until API side issues were fixed. This PR enables alerts in DABs again.
I had to regenerate openapi annotations and the pydabs code because the linter was complaining. It seems that we do not automatically update these.
Tests
Now the acceptance test is also run on cloud.