Skip to content

Conversation

@rileymccuen-nonemu-dropbox

Changes

Add run_as support for alerts in Databricks Asset Bundles.

Previously, alerts were in the deny list for run_as configuration, meaning bundles with alerts would fail validation when a run_as identity was specified. This PR:

  1. Removes alerts from the validation check that errors when run_as is set
  2. Adds a new setRunAsForAlerts function that propagates the bundle's run_as configuration to alert resources via the AlertV2RunAs struct
  3. Updates tests to include alerts in the allowed resources test case

Why

Alerts now support the run_as field in the API via the AlertV2RunAs struct, which accepts ServicePrincipalName or UserName. This change allows users to configure alerts with a specific run_as identity, consistent with how jobs and pipelines handle run_as.

Tests

  • Updated TestRunAsWorksForAllowedResources to include an alert resource
  • Added alerts to the allowList in TestRunAsErrorForUnsupportedResources
  • Existing unit tests pass

@github-actions
Copy link

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

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 4360
  • Commit SHA: acd3520b6a5e6b7b42f5cd1c44dfe1b943977b10

Checks will be approved automatically on success.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant