cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

DAB deploy missing packages

Przemk00
New Contributor II

Hello everyone, not sure where to start but so will do it from the beginning. 

I encountered an issue where my .whl files in the dist/ and packages/ directories were not being deployed to Databricks using dab-deploy. After investigating, I discovered that these directories were listed in .gitignore, which prevented them from being included in the deployment. As a workaround, commenting out the dist/ and packages/ entries in .gitignore ensures the deployment is successful.

The question arises why for some it works and for others, it does not and has to do some workarounds.

Thanks,

 

5 REPLIES 5

-werners-
Esteemed Contributor III

it could be depending on the template you used when creating the package.
DAB is still rough around the edges.

Przemk00
New Contributor II

Is there anything specific I should look in the template? 

-werners-
Esteemed Contributor III

In your case it would be what is in the .gitignore file.
Somehow your files were ignored, and if you did not edit the .gitignore, it was probably copied from a template (or existing dab).

saurabh18cs
Contributor II

Production native approach is to maintain your artifacts in central antifactory and use this location in your .yml for libraries. This way you ensure your antifactory are properly versioned , governed and maintaining some sort of standards. I hope with this approach you can reduce your errors of missing packages/whl etc.

 

e.g.

 
        libraries:
        - pypi:
            packagerequests==2.31.0
        - pypi:
            packageazure-eventhub==5.10.1
        - pypi:
            packageazure-identity==1.12.0
        - pypi:
            package: yourpackage==0.0.0
        

saurabh18cs
Contributor II

Production native approach is to maintain your artifacts in central antifactory and use this location in your .yml for libraries. This way you ensure your antifactory are properly versioned , governed and maintaining some sort of standards. I hope with this approach you can reduce your errors of missing packages/whl etc.

e.g.

        libraries:
        - pypi:
            packagerequests==2.31.0
        - pypi:
            package: yourpackage==0.0.0

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group