Skip to content
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

Ignore "develop = true" #9369

Open
idan3 opened this issue May 2, 2024 · 0 comments
Open

Ignore "develop = true" #9369

idan3 opened this issue May 2, 2024 · 0 comments
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged

Comments

@idan3
Copy link

idan3 commented May 2, 2024

Issue Kind

Brand new capability

Description

I know this issue came up here several times but I couldn't find a good solution for that.
Let's say I'm using the following dependency:

[tool.poetry.dependencies]
my_lib = {path = "../../my_lib", develop = true}

when I deploy to production I want it to run without develop = true but it doesn't seems there is an option to do so.
I don't want to split it into another group because this will mean duplicating all my dependencies (which I develop locally) and this does not make any sense.

Shouldn't there be some --production flag to solve this problem?

Impact

Currently, I need to workaround or duplicate 19 dependencies.

Workarounds

A script that changes the develop = true to false on the deployment pipeline.

@idan3 idan3 added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

1 participant