-
-
Notifications
You must be signed in to change notification settings - Fork 376
There was a dependency between python::virtualenv and python::requirements. Basically, the virtualenv wanted to initialize requirements, but requirements depended on the virtualenv being created already, resulting in: err: Could not apply complete catalog: Found 1 dependency cycle: (Exec[python_requirements_check_/usr/share/err/repo/requirements.txt] => Python::Requirements[/usr/share/err/repo/requirements.txt] => Exec[python_virtualenv_/usr/share/err/python3] => Python::Requirements[/usr/share/err/repo/requirements.txt] => Exec[python_requirements_check_/usr/share/err/repo/requirements.txt])
Allow virtualenv definitions to share the same requirements file
|
Thanks! |
Allow virtualenv definitions to share the same requirements file
I wanted to do the following, but this causes resources to be declared twice:
With these changes, this is now possible. Note that this pull request automatically brings in the commit from #4 so if you do not intend to merge this one, let me know and I will pull those changes out of it.