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

Can't use InSpec AWS resources due to Gem dependency constraint #185

Closed
walterdolce opened this issue Jun 19, 2018 · 1 comment
Closed

Comments

@walterdolce
Copy link
Contributor

Hi,

It is currently not possible to upgrade InSpec to anything >= 2.0.0 due to the fact there is a constraint in the gemspec.

I have the following Gemfile is in place:

source "https://rubygems.org"

gem "test-kitchen", "1.21.2"
gem "kitchen-docker", "2.6.0"
gem "kitchen-inspec", "0.18.0"
gem "kitchen-ansible", "0.48.5"

Which gives me the following version of InSpec:

# bundler output
Using inspec 1.51.25
# bundler output

If I try to explicitly up InSpec's version, I am expectedly prevented from doing so because...

  In Gemfile:
    inspec (= 2.2.16)

    kitchen-inspec (= 0.18.0) was resolved to 0.18.0, which depends on
      inspec (< 2.0.0, >= 0.34.0)

Does kitchen-inspec need upgrading along with InSpec? Or can a PR to change the constraint from 2.0.0 to 3.0.0 be sent?

Thank you,

@walterdolce
Copy link
Contributor Author

walterdolce commented Jun 19, 2018

Forget this. I didn't see "Show newer tags" on the release page, above the 0.18.0 big blue tag :D

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

1 participant