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

pulumi-kubernetes dependency pinning on PyYAML is incompatibe with pulumi dependencies #1767

Closed
arni-inaba opened this issue Oct 14, 2021 · 1 comment · Fixed by #1768
Closed
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@arni-inaba
Copy link

arni-inaba commented Oct 14, 2021

Hello!

  • Vote on this issue by adding a 👍 reaction
  • To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

The PyYAML pinning for pulumi and pulumi-kubernetes broke today when PyYAML 6.0 was released.

pulumi asks for pyyaml>=5.3.1

pulumi-kubernetes requires pyyaml<6.0,>=5.3.1

Steps to reproduce

  1. pip install recent version of pulumi
  2. pip install recent version of pulumi-kubernetes
  3. observe the error:
pulumi-kubernetes 3.5.0 requires pyyaml<6.0,>=5.3.1, but you'll have pyyaml 6.0 which is incompatible.

Expected: I expected pulumi-kubernetes to be installed
Actual: An error

Workaround: Explicitly specify a PyYAML version in your requirements, e.g. PyYAML==5.4.1

@arni-inaba arni-inaba added the kind/bug Some behavior is incorrect or out of spec label Oct 14, 2021
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Oct 15, 2021
@eirikur-grid
Copy link

I think there's a perfect opportunity for test automation here. Not being able to pip install a typical combination of pulumi packages leads to user frustration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants