Closed morganchorlton3 closed 2 weeks ago
How about simplifying things a bit, and just accept a poetry_args
string that's directly added to the poetry command?
Hi @pdecat yeah I can make that change
How about simplifying things a bit, and just accept a
poetry_args
string that's directly added to the poetry command?
Change applied 👍
PR should be renamed, e.g. feat: Support passing extra args to poetry export
.
This PR is included in version 7.6.0 :tada:
Description
I have added support to pass additional poetry arguments into the source paths
closes #500
Motivation and Context
I have a project with a mono-repo approach with multiple lambda functions in the project, I have some separate list of dependencies defined in my pyproject.toml. I want to install additional dependencies for certain lambda functions for example
Lambda function 1 deps: ...
Lambda function 2 deps: ....
Common function deps: ....
I could then install the common deps for all lambda functions and then install specific deps for each lambda functions.
Breaking Changes
None that i am aware off
How Has This Been Tested?
[ ] I have updated at least one of the
examples/*
to demonstrate and validate my change(s) (I can do this if it would help, what would be the best to update/ should i add a new example?)I have tested these changes locally with a local project deploying a lambda with and without groups defined
I am happy to do additional testing if required.
pre-commit run -a
on my pull request (see screenshot)