Affected Puppet, Ruby, OS and module versions/distributions
Puppet: v5.5.14
Ruby: 2.4.5p335
Distribution: Centos 7
Module version: 2.2.3-rc0
How to reproduce (e.g Puppet code you use)
If you create venvs in two different modules which depend on each other and install packages via python::pip, dependency cycle appears as all venvs are requirements for each python::pip.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
If you create venvs in two different modules which depend on each other and install packages via python::pip, dependency cycle appears as all venvs are requirements for each python::pip.
What behaviour did you expect instead
Python:;pip should depend only on venvs it uses.
Any additional information you'd like to impart
Affecting lines start at https://github.com/voxpupuli/puppet-python/blob/master/manifests/pip.pp#L75. Those collectors should probably limit venv by path.