Open fortman opened 4 years ago
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!
Version 1.1.3 fixed our issues, we're rolling out that restriction again ASAP!
Vault gem version 0.13.2 was released. This should no longer be a problem. Let me know if it still is @fortman
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)