<?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: Passing Different Job Parameters or Environment Variables Based on Targets in DABs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112783#M44325</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/153721"&gt;@azam-io&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Please find the best practices here for deploying jobs using Asset Bundles configuration:&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/dev-tools/bundles/settings" target="_blank"&gt;https://docs.databricks.com/aws/en/dev-tools/bundles/settings&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you would like to pass different parameters for your same job in different environments, you can segregate the jobs with respective configurations in respective target folders as below:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dev   ## folder containing respective jobs to be deployed in DEV
acc   ## folder containing respective jobs to be deployed in ACC
prd   ## folder containing respective jobs to be deployed in PRD
bundles.target.yml ## Here you are maintaining configurations for different environment&lt;/LI-CODE&gt;&lt;P&gt;By having this approach you can pass different parameters to same job in different environments. In your bundles target, hopefully you will be pointing the respective environment variables for each envs.&lt;BR /&gt;&lt;BR /&gt;Please let us know if you find this helpful or additional clarifications required.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Nivethan V&lt;/P&gt;</description>
    <pubDate>Mon, 17 Mar 2025 10:10:05 GMT</pubDate>
    <dc:creator>Nivethan_Venkat</dc:creator>
    <dc:date>2025-03-17T10:10:05Z</dc:date>
    <item>
      <title>Passing Different Job Parameters or Environment Variables Based on Targets in DABs</title>
      <link>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112754#M44318</link>
      <description>&lt;P&gt;Hi, I am currently using DABs in my project and have encountered an issue. Specifically, I need to pass different job parameters or environment variables depending on the target and for specific jobs.&lt;BR /&gt;Could you please provide guidance on how to approach this, or any best practices for handling this scenario?&lt;BR /&gt;Thank You&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 05:24:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112754#M44318</guid>
      <dc:creator>azam-io</dc:creator>
      <dc:date>2025-03-17T05:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Passing Different Job Parameters or Environment Variables Based on Targets in DABs</title>
      <link>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112783#M44325</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/153721"&gt;@azam-io&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Please find the best practices here for deploying jobs using Asset Bundles configuration:&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/dev-tools/bundles/settings" target="_blank"&gt;https://docs.databricks.com/aws/en/dev-tools/bundles/settings&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you would like to pass different parameters for your same job in different environments, you can segregate the jobs with respective configurations in respective target folders as below:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dev   ## folder containing respective jobs to be deployed in DEV
acc   ## folder containing respective jobs to be deployed in ACC
prd   ## folder containing respective jobs to be deployed in PRD
bundles.target.yml ## Here you are maintaining configurations for different environment&lt;/LI-CODE&gt;&lt;P&gt;By having this approach you can pass different parameters to same job in different environments. In your bundles target, hopefully you will be pointing the respective environment variables for each envs.&lt;BR /&gt;&lt;BR /&gt;Please let us know if you find this helpful or additional clarifications required.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Nivethan V&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 10:10:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112783#M44325</guid>
      <dc:creator>Nivethan_Venkat</dc:creator>
      <dc:date>2025-03-17T10:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: Passing Different Job Parameters or Environment Variables Based on Targets in DABs</title>
      <link>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112793#M44329</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/148397"&gt;@Nivethan_Venkat&lt;/a&gt;,&amp;nbsp;thanks for your response, it's quite helpful. However i would like to know if there is any way to define those variables inside the resource file of the job instead of defining them in separate folders. You know like we do inside targets tag.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Azam Ali&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 11:31:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/passing-different-job-parameters-or-environment-variables-based/m-p/112793#M44329</guid>
      <dc:creator>azam-io</dc:creator>
      <dc:date>2025-03-17T11:31:30Z</dc:date>
    </item>
  </channel>
</rss>

