[ISSUE] Issue with databricks_alert resource

[mathiaspetersepi]

The example code of the databricks_alert resource creates a broken alert. The condition is not evaluated correctly.
I am using aquery which returns a single integer column "number_of_events". I want to trigger the alert if the attribute value of the first row is 0.
The documentation does not show any options to configure the first row into the trigger condition.

Configuration

resource "databricks_alert" "raw_wallets_empty_alert" {
  query_id     = databricks_query.monitoring_query_wallets.id
  display_name = "Raw Wallets stale for 12 hrs"
  parent_path  = databricks_directory.shared_dir.path

  condition {
    op = "EQUAL"
    operand {
      column {
        name = "number_of_events"
      }
    }
    threshold {
      value {
        double_value = 0
      }
    }
    empty_result_state = "OK"
  }
}

Expected Behavior

The evaluation criterion should be displayed correctly.

Actual Behavior

The trigger condition is broken.

[alexott]

it looks like it a problem with API - I don't see any option for specifying first row and other params: https://docs.databricks.com/api/workspace/alerts/create

[alexott]

I chatted with the dev team - the "First Row" is the default operation. The gap in that API is known, but there is no ETA for adding it.

[mathiaspetersepi]

Since I followed the terraform example: does that mean the resource is broken or did I use it incorrectly?

[alexott]

Ok, I dug deeper into it - the problem is caused by having omitempty on the attribute definition. This causes the 0 value not to be sent as a payload because TF SDK doesn't distinguish between the 0 value that is specified and if it's not specified at all:

<   "condition": {
<     "empty_result_state": "OK",
<     "op": "EQUAL",
<     "operand": {
<       "column": {
<         "name": "count"
<       }
<     },
<     "threshold": {
<       "value": {}
<     }
<   },

Unfortunately, this could be solved only by porting this resource to the TF plugin framework that allows to distinguish between the 0 value that is set and not specified value.

The current workaround would be to use string_value = "0" instead (similarly for string_value = "false" for bool_value = false).

[mathiaspetersepi]

Can confirm, that this workaround does the trick. Thank you