<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Asset Bundles Email/Notifications Prod ONly in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113201#M44464</link>
    <description>&lt;P&gt;This is exactly what I did! Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 20 Mar 2025 18:34:38 GMT</pubDate>
    <dc:creator>rriley2</dc:creator>
    <dc:date>2025-03-20T18:34:38Z</dc:date>
    <item>
      <title>Asset Bundles Email/Notifications Prod ONly</title>
      <link>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113085#M44420</link>
      <description>&lt;P&gt;Howdy,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've got a job 'job1' and my dev/stg/prod target in my databricks.yaml&lt;/P&gt;&lt;P&gt;Currently, I have this configurationfor&amp;nbsp; my job:&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;email_notifications&lt;/SPAN&gt;:&lt;BR /&gt;&lt;SPAN&gt; on_success&lt;/SPAN&gt;:&lt;BR /&gt;  - me@myorg.com&lt;BR /&gt;&lt;SPAN&gt; on_failure&lt;/SPAN&gt;:&lt;BR /&gt;  - me@myorg.com&lt;BR /&gt;&lt;SPAN&gt;webhook_notifications&lt;/SPAN&gt;:&lt;BR /&gt;&lt;SPAN&gt; on_failure&lt;/SPAN&gt;:&lt;BR /&gt;  - &lt;SPAN&gt;id&lt;/SPAN&gt;: ${var.webhook_uuid}&lt;/PRE&gt;&lt;P&gt;I'd like to ultimately like the following conditions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;dev: nothing, this is paused (solved this problem already)&lt;/LI&gt;&lt;LI&gt;stg: email only on failure&lt;/LI&gt;&lt;LI&gt;prod: email on success and failure, webhook on failure.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I've tried just setting the variable to be empty and this is a violation in the databricks validate task.&lt;/P&gt;&lt;P&gt;I've tried setting the webhook uuid to some junk and that also fails.&lt;/P&gt;&lt;P&gt;Any advice would be lovely!&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 19 Mar 2025 20:45:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113085#M44420</guid>
      <dc:creator>rriley2</dc:creator>
      <dc:date>2025-03-19T20:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: Asset Bundles Email/Notifications Prod ONly</title>
      <link>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113098#M44424</link>
      <description>&lt;P&gt;Hi rriley2,&lt;/P&gt;&lt;P&gt;How are you doing today?, As per my understanding,&amp;nbsp;Yeah, Databricks doesn’t allow empty values for email_notifications or webhook_notifications, so the trick is to use YAML conditionals and defaults to handle different environments without validation errors. A good way to do this is by setting up YAML anchors to define common notification settings and then overriding them per environment. For example, in dev, you can just set {} for both email and webhook to disable notifications. In stg, keep email only for failures, and in prod, enable both success/failure emails and webhook on failure. This avoids using junk values while keeping the config clean and flexible. Let me know if you need a sample YAML file—I’ve got you covered!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brahma&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 03:30:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113098#M44424</guid>
      <dc:creator>Brahmareddy</dc:creator>
      <dc:date>2025-03-20T03:30:33Z</dc:date>
    </item>
    <item>
      <title>Re: Asset Bundles Email/Notifications Prod ONly</title>
      <link>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113100#M44426</link>
      <description>&lt;P&gt;Hmmm so something like this:&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;targets&lt;/SPAN&gt;:&lt;BR /&gt;  &lt;SPAN&gt;dev&lt;/SPAN&gt;:&lt;BR /&gt;    &lt;SPAN&gt;resources&lt;/SPAN&gt;:&lt;BR /&gt;      &lt;SPAN&gt;jobs&lt;/SPAN&gt;:&lt;BR /&gt;        &lt;SPAN&gt;Workflow1&lt;/SPAN&gt;:&lt;BR /&gt;          &lt;SPAN&gt;email_notifications&lt;/SPAN&gt;: {}&lt;BR /&gt;          &lt;SPAN&gt;webhook_notifications&lt;/SPAN&gt;: {}&lt;BR /&gt;  &lt;SPAN&gt;stage&lt;/SPAN&gt;:&lt;BR /&gt;    &lt;SPAN&gt;resources&lt;/SPAN&gt;:&lt;BR /&gt;      &lt;SPAN&gt;jobs&lt;/SPAN&gt;:&lt;BR /&gt;        &lt;SPAN&gt;Workflow1&lt;/SPAN&gt;:&lt;BR /&gt;          &lt;SPAN&gt;email_notifications&lt;/SPAN&gt;:&lt;BR /&gt;            &lt;SPAN&gt;on_success&lt;/SPAN&gt;:&lt;BR /&gt;              - me@myorg.com&lt;BR /&gt;            &lt;SPAN&gt;on_failure&lt;/SPAN&gt;:&lt;BR /&gt;              - me@myorg.com&lt;BR /&gt;          &lt;SPAN&gt;webhook_notifications&lt;/SPAN&gt;:&lt;BR /&gt;            &lt;SPAN&gt;on_failure&lt;/SPAN&gt;:&lt;BR /&gt;              - &lt;SPAN&gt;id&lt;/SPAN&gt;: stg_id&lt;BR /&gt;  &lt;SPAN&gt;prod&lt;/SPAN&gt;:&lt;BR /&gt;    &lt;SPAN&gt;resources&lt;/SPAN&gt;:&lt;BR /&gt;      &lt;SPAN&gt;jobs&lt;/SPAN&gt;:&lt;BR /&gt;        &lt;SPAN&gt;Workflow1&lt;/SPAN&gt;:&lt;BR /&gt;          &lt;SPAN&gt;email_notifications&lt;/SPAN&gt;:&lt;BR /&gt;            &lt;SPAN&gt;on_success&lt;/SPAN&gt;:&lt;BR /&gt;              - me@myorg.com&lt;BR /&gt;            &lt;SPAN&gt;on_failure&lt;/SPAN&gt;:&lt;BR /&gt;              - me@myorg.com&lt;BR /&gt;          &lt;SPAN&gt;webhook_notifications&lt;/SPAN&gt;:&lt;BR /&gt;            &lt;SPAN&gt;on_failure&lt;/SPAN&gt;:&lt;BR /&gt;              - &lt;SPAN&gt;id&lt;/SPAN&gt;: prod_id&lt;/PRE&gt;&lt;P&gt;So I would have to push the resource into the target keys to add environment variance. That makes sense. If I get this to work, I will post again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 20 Mar 2025 03:49:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113100#M44426</guid>
      <dc:creator>rriley2</dc:creator>
      <dc:date>2025-03-20T03:49:33Z</dc:date>
    </item>
    <item>
      <title>Re: Asset Bundles Email/Notifications Prod ONly</title>
      <link>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113201#M44464</link>
      <description>&lt;P&gt;This is exactly what I did! Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 18:34:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/asset-bundles-email-notifications-prod-only/m-p/113201#M44464</guid>
      <dc:creator>rriley2</dc:creator>
      <dc:date>2025-03-20T18:34:38Z</dc:date>
    </item>
  </channel>
</rss>

