Unfortunately at present imported projects are not included in a model when the environment for that model is built. This is similar to the way models don't read requirments.txt.
For now, the work-around is either to copy the code from your imported projects to the model's project before publishing the model API or to upload the code in your imported projects to an external Git repository (such as GitHub) and import the code to you model via the external Git repository using the work-around I linked to above.
Comments
1 comment
Unfortunately at present imported projects are not included in a model when the environment for that model is built. This is similar to the way models don't read requirments.txt (a work-around for which you can find here: https://community.dominodatalab.com/discussion/167/how-do-i-ensure-a-python-package-from-a-private-repo-is-usable-in-both-runs-and-models#latest)
I will make sure the documentation is updated to make it clear that imported projects are not read at present and also we'll work on making this work as expected in the future.
For the moment, the work-around is either to copy the code from your imported projects to the model's project before publishing the model API or to upload the code in your imported projects to an external Git repository (such as GitHub) and import the code to you model via the external Git repository using the work-around I linked to above.
Submitted by: terry.stebbens
Please sign in to leave a comment.