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

Version conflict with gem dependency aws-sigv4 #233

Open
fortman opened this issue May 7, 2020 · 3 comments
Open

Version conflict with gem dependency aws-sigv4 #233

fortman opened this issue May 7, 2020 · 3 comments

Comments

@fortman
Copy link

fortman commented May 7, 2020

We are loading the vault-ruby gem with Chef. Either Chef directly or some other dependency is also loading aws-sigv4, but version 1.1.3. I believe it is Chef itself loading it, as it is happening on new system installs with the first Chef run. Is there any way to move this runtime dependency to be 1.1.x instead of pinned to 1.1.1? The aws gems get updated all the time, so I would think you'd want the latest 1.1 version.

Unable to activate vault-0.13.1, because aws-sigv4-1.1.3 conflicts with aws-sigv4 (= 1.1.1)

@Valarissa
Copy link
Contributor

Version 1.1.2 caused some errors in our build path, I will check version 1.1.3 to see if it was a problem with the 1.1.2 version. Thanks for bringing this up!

@Valarissa
Copy link
Contributor

Version 1.1.3 fixed our issues, we're rolling out that restriction again ASAP!

@Valarissa
Copy link
Contributor

Vault gem version 0.13.2 was released. This should no longer be a problem. Let me know if it still is @fortman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants