-
-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Support passing extra args to poetry export #584
feat: Support passing extra args to poetry export #584
Conversation
How about simplifying things a bit, and just accept a |
Hi @pdecat yeah I can make that change |
Change applied 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall! One last comment about the naming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
PR should be renamed, e.g. |
## [7.6.0](v7.5.0...v7.6.0) (2024-06-12) ### Features * Support passing extra args to poetry export ([#584](#584)) ([3aa288f](3aa288f))
This PR is included in version 7.6.0 🎉 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
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?
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)