We have a dbt project that is being used as a package in other dbt projects. The requirement for us is that the code of the dbt package should not be accessible to the users who are importing them but they should still be able to use the package. Is there a possibility in dbt to achieve this behaviour? Any thoughts/suggestions would really help.
Thanks.
Sounds like the folks making that a requirement doesn’t really understand dbt imho. dbt is just SQL+Jinja - I don’t think you can really package it up in a way that hides it from your users.
Note: @Jeremy Yeo originally posted this reply in Slack. It might not have transferred perfectly.
Or I guess if you’re producing a table - just have them use it as a source or something so you’re not exposing the SQL code used to build the model. But if you’re sharing macros, you may be out of luck with this obfuscation exercise.
Note: @Jeremy Yeo originally posted this reply in Slack. It might not have transferred perfectly.