<?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: Declarative Pipeline Asset Bundle Root Folder in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122734#M46851</link>
    <description>&lt;P&gt;Thank you, Ilir. I missed that. That solved my issue.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Jun 2025 19:08:59 GMT</pubDate>
    <dc:creator>ceediii</dc:creator>
    <dc:date>2025-06-24T19:08:59Z</dc:date>
    <item>
      <title>Declarative Pipeline Asset Bundle Root Folder</title>
      <link>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122569#M46814</link>
      <description>&lt;P&gt;Hi everyone&lt;/P&gt;&lt;P&gt;In the new declarative pipeline UI (preview), we have the option to define a root folder.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ceediii_0-1750694376542.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/17703i586EBBB49FAC4FDC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ceediii_0-1750694376542.png" alt="ceediii_0-1750694376542.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;My ressource asset bundle is currently defined as:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;resources:
  jobs:
    my_job:
      name: "(${var.branch}) my_job" 
      tasks:
        - task_key: my_pipeline
          pipeline_task:
            pipeline_id: ${resources.pipelines.my_pipeline.id}
          
  pipelines:
    my_pipeline:
      name: "(${var.branch}) my_pipeline"
      clusters:
        ... cluster setup
      catalog: "${var.catalog_silver}"
      schema: my_schema
      target: my_schema
      development: false
      continuous: false
      channel: CURRENT
      edition: CORE
      photon: true
      serverless: false
      libraries:
        - file:
            path: ${workspace.file_path}/src/silver/path_to_my_file/my_file.py
      configuration:
        bronze_catalog: "${var.catalog_bronze}"
        bronze_schema: my_schema
      root_path: "${workspace.file_path}/src"&lt;/LI-CODE&gt;&lt;P&gt;But the root_path is not set during deployment. I have also tried it with root_folder as the key and tried to set it with the filter.include property but I can't get it working.&lt;/P&gt;&lt;P&gt;Does anyone know how to properly set this up in the asset bundle?&lt;/P&gt;&lt;P&gt;Thank you for your support.&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jun 2025 16:05:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122569#M46814</guid>
      <dc:creator>ceediii</dc:creator>
      <dc:date>2025-06-23T16:05:26Z</dc:date>
    </item>
    <item>
      <title>Re: Declarative Pipeline Asset Bundle Root Folder</title>
      <link>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122619#M46832</link>
      <description>&lt;P&gt;Hello ceediii,&lt;BR /&gt;&lt;BR /&gt;The root_path property under individual resource is not supported and it will be ignored. You would need&lt;BR /&gt;to specify it on workspace level, example of databricks.yml file with root_path changed:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;targets:
  # The 'dev' target, for development purposes. This target is the default.
  develop:
    # We use 'mode: development' to indicate this is a personal development copy:
    # - Deployed resources get prefixed with '[dev my_user_name]'
    # - Any job schedules and triggers are paused by default
    # - The 'development' mode is used for Delta Live Tables pipelines
    # mode: development you get an error if you enable dev mode with root_path specified
    default: true
    workspace:
      host: https://&amp;lt;databricks_host&amp;gt;.net 
      root_path: /Workspace/Shared/&amp;lt;your_folder&amp;gt; #e.g. If you wanna have in shared folder&lt;/LI-CODE&gt;&lt;P&gt;Hope that helps. Let me know if you need anything else to clarify.&lt;BR /&gt;&lt;BR /&gt;Best,&lt;/P&gt;&lt;P&gt;Ilir&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jun 2025 08:03:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122619#M46832</guid>
      <dc:creator>ilir_nuredini</dc:creator>
      <dc:date>2025-06-24T08:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: Declarative Pipeline Asset Bundle Root Folder</title>
      <link>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122734#M46851</link>
      <description>&lt;P&gt;Thank you, Ilir. I missed that. That solved my issue.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jun 2025 19:08:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122734#M46851</guid>
      <dc:creator>ceediii</dc:creator>
      <dc:date>2025-06-24T19:08:59Z</dc:date>
    </item>
    <item>
      <title>Re: Declarative Pipeline Asset Bundle Root Folder</title>
      <link>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122747#M46855</link>
      <description>&lt;P&gt;You are welcome, great it helped!&lt;BR /&gt;&lt;BR /&gt;Best, Ilir&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jun 2025 23:37:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/declarative-pipeline-asset-bundle-root-folder/m-p/122747#M46855</guid>
      <dc:creator>ilir_nuredini</dc:creator>
      <dc:date>2025-06-24T23:37:17Z</dc:date>
    </item>
  </channel>
</rss>

