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
I have searched the issues of this repo and believe that this is not a duplicate.
I have searched the documentation and believe that my question is not covered.
Feature Request
this request follows #4086.
the keyrings.google-artifactregistry-auth package must be installed before the private repo source can be authenticated
its also not strictly speaking a dependency of the current project
Possible implementation 1
given the following configuration, whenever this secondary source is loaded, keyrings.google-artifactregistry-auth would be installed
[[tool.poetry.source]]
name = "my_pypi"url = "https://europe-west2-python.pkg.dev/my-gcp-project/mypypi/simple"secondary = truerequires = ["keyrings.google-artifactregistry-auth==1.0.0"]
the downside of this is that dependency resolution would have to be done multiple times?
Possible implementation 2
given the following configuration, when the venv is first spun up, before any secondary sources are loaded, the venv_bootstrap_commands are executed
[tool.poetry]
name = "poetry-demo"version = "0.1.0"venv_bootstrap_commands =
pip install keyrings.google-artifactregistry-auth==1.0.0
The text was updated successfully, but these errors were encountered:
I don't think your suggestions would work. If the keyrings.google-artifactregistry-auth package is needed for an authentification it must be installed in the environment where poetry is running and not in the venv of the project.
When poetry is installed with pipx one could install the necessary package into the same environment using pipx inject.
An alternative might be to create a Poetry Plugin that do nothing but add a new dependency into the Poetry environment.
Feature Request
this request follows #4086.
the
keyrings.google-artifactregistry-auth
package must be installed before the private repo source can be authenticatedits also not strictly speaking a dependency of the current project
Possible implementation 1
given the following configuration, whenever this secondary source is loaded, keyrings.google-artifactregistry-auth would be installed
the downside of this is that dependency resolution would have to be done multiple times?
Possible implementation 2
given the following configuration, when the venv is first spun up, before any secondary sources are loaded, the
venv_bootstrap_commands
are executedThe text was updated successfully, but these errors were encountered: