<?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 Asset bundle build and deploy python wheel with versions in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/asset-bundle-build-and-deploy-python-wheel-with-versions/m-p/55266#M1990</link>
    <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;I was able to deploy a wheel to the&amp;nbsp;&lt;SPAN&gt;/Shared/ folder from a repository in Gitlab with asset bundles. The databricks.yml looks something like this.&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;artifacts:&lt;BR /&gt;&amp;nbsp; default:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; type: whl&lt;BR /&gt;&amp;nbsp; &amp;nbsp; build: poetry build&lt;BR /&gt;&amp;nbsp; &amp;nbsp; path: .&lt;BR /&gt;&amp;nbsp; targets:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; workspace:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; host: ***&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; root_path: /Shared/.bundle/...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;The build happens and it stores the wheel here,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;/Shared/.bundle/library/artifacts/.internal/&amp;lt;hash&amp;gt;/&amp;lt;file-name&amp;gt;.whl&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;What I would like to have is some sort of versioning of package deployments. The problems that prevents this to happen are:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;At each deployment the previous deployed files are removed (no versioning)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;The path to the wheel contains a hash that keeps changing, so it's hard to point to it&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;How would you proceed?&lt;/DIV&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 14 Dec 2023 17:16:55 GMT</pubDate>
    <dc:creator>pablobd</dc:creator>
    <dc:date>2023-12-14T17:16:55Z</dc:date>
    <item>
      <title>Asset bundle build and deploy python wheel with versions</title>
      <link>https://community.databricks.com/t5/get-started-discussions/asset-bundle-build-and-deploy-python-wheel-with-versions/m-p/55266#M1990</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;I was able to deploy a wheel to the&amp;nbsp;&lt;SPAN&gt;/Shared/ folder from a repository in Gitlab with asset bundles. The databricks.yml looks something like this.&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;artifacts:&lt;BR /&gt;&amp;nbsp; default:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; type: whl&lt;BR /&gt;&amp;nbsp; &amp;nbsp; build: poetry build&lt;BR /&gt;&amp;nbsp; &amp;nbsp; path: .&lt;BR /&gt;&amp;nbsp; targets:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; workspace:&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; host: ***&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; root_path: /Shared/.bundle/...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;The build happens and it stores the wheel here,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;/Shared/.bundle/library/artifacts/.internal/&amp;lt;hash&amp;gt;/&amp;lt;file-name&amp;gt;.whl&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;What I would like to have is some sort of versioning of package deployments. The problems that prevents this to happen are:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;At each deployment the previous deployed files are removed (no versioning)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;The path to the wheel contains a hash that keeps changing, so it's hard to point to it&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;How would you proceed?&lt;/DIV&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 17:16:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/asset-bundle-build-and-deploy-python-wheel-with-versions/m-p/55266#M1990</guid>
      <dc:creator>pablobd</dc:creator>
      <dc:date>2023-12-14T17:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Asset bundle build and deploy python wheel with versions</title>
      <link>https://community.databricks.com/t5/get-started-discussions/asset-bundle-build-and-deploy-python-wheel-with-versions/m-p/55308#M1997</link>
      <description>&lt;P&gt;Finally I decided to use&amp;nbsp;&lt;SPAN&gt;AWS Code Artifact and mirror the PyPI, which I think it's a bit cleaner. But your solution looks good too. Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2023 09:51:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/asset-bundle-build-and-deploy-python-wheel-with-versions/m-p/55308#M1997</guid>
      <dc:creator>pablobd</dc:creator>
      <dc:date>2023-12-15T09:51:22Z</dc:date>
    </item>
  </channel>
</rss>

