You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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!
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)
The text was updated successfully, but these errors were encountered: