You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have code to package and deploy third party libraries, but it might be cool to have SA package its own dependencies (from requirements.txt) into the deployment archive as well. #40 introduced a new lambda dependency, and other revisions likely will too.
We could track these in third_party_libs in variables.json but IMO those should just be the dependencies of the rules themselves rather than their underlying infrastructure.
The text was updated successfully, but these errors were encountered:
We already have code to package and deploy third party libraries, but it might be cool to have SA package its own dependencies (from
requirements.txt
) into the deployment archive as well. #40 introduced a new lambda dependency, and other revisions likely will too.We could track these in
third_party_libs
invariables.json
but IMO those should just be the dependencies of the rules themselves rather than their underlying infrastructure.The text was updated successfully, but these errors were encountered: