Repository navigation
Add support for configuring app health_check via bundle config - #7081
arushiagarwal-db wants to merge 3 commits into
Conversation
Adds `health_check` (path, timeout_seconds) to the inline app `config` block and passes it to the Apps Deploy API as `health_check`. Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
|
Thanks for the contribution! This pull request was opened from a fork. If you're a member of the Databricks organization, please request access to the If you're an external contributor, no action is needed; a maintainer will review your pull request. |
|
An authorized user can trigger integration tests manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
|
This PR has not received an update in a while. If you want to keep this PR open, please leave a comment below or push a new commit and auto-close will be canceled. |
Changes
Add
health_checkto the inline appconfigblock for apps in bundle config:The value is passed to the Apps Deploy API's new
health_checkfield (path,timeout). The fields matchhealth_checkin app.yaml (path,timeout_seconds), sodatabricks apps importalso inlineshealth_checkfrom an existing app.yaml. The direct engine readshealth_checkback from the active deployment for drift detection, the same way it does forcommandandenv.Why
This follows #4271 (inline
command/env). It lets users set the deploy-time health check per target in bundle config, without keeping it in a separate app.yaml.Tests
acceptance/bundle/resources/apps/inline_configacceptance test with ahealth_checkand a/healthroute in the test app.TestBuildAppDeploymentWithValueFromandTestInlineAppConfigFileFieldPriorityunit tests.This pull request and its description were written by Isaac.