Skip to content

Add support for configuring app health_check via bundle config - #7081

Draft
arushiagarwal-db wants to merge 2 commits into
databricks:mainfrom
arushiagarwal-db:arushi-agarwal/apps-inline-health-check
Draft

arushiagarwal-db wants to merge 2 commits into
databricks:mainfrom
arushiagarwal-db:arushi-agarwal/apps-inline-health-check

Conversation

@arushiagarwal-db

Copy link
Copy Markdown

Changes

Add health_check to the inline app config block for apps in bundle config:

resources:
  apps:
    myapp:
      source_code_path: ./app
      config:
        command: ["flask", "--app", "app", "run"]
        health_check:
          path: /health
          timeout_seconds: 120

The value is passed to the Apps Deploy API's new health_check field (path, timeout). The fields match health_check in app.yaml (path, timeout_seconds), so databricks apps import also inlines health_check from an existing app.yaml. The direct engine reads health_check back from the active deployment for drift detection, the same way it does for command and env.

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

  • Extended the acceptance/bundle/resources/apps/inline_config acceptance test with a health_check and a /health route in the test app.
  • Extended TestBuildAppDeploymentWithValueFrom and TestInlineAppConfigFileFieldPriority unit tests.
  • Regenerated refschema, JSON schema, and required-fields validation.

This pull request and its description were written by Isaac.

Arushi Agarwal and others added 2 commits October 15, 2026 18:01
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>
@github-actions github-actions Bot added the DABs DABs related issues label Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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 cli-contrib team and open your pull request from a branch in this repository instead of a fork — fork PRs don't run integration tests automatically and have reduced CI access.

If you're an external contributor, no action is needed; a maintainer will review your pull request.

@github-actions

Copy link
Copy Markdown
Contributor

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 7081
  • Commit SHA: b98c6f23fc9d6828d13ae20eb62b8a3ded5e348c

Checks will be approved automatically on success.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DABs DABs related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant