-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
InSpec breaks with ActiveSupport 7.1.0 #750
Comments
There is a larger discussion around this here on rails/rails: rails/rails#49495 (comment) There is a related cocoapods issue, so there may be learnings to be gathered here: CocoaPods/CocoaPods#12082 e.g. ensure requires are happening for activesupport when used outside of rails ecosystem |
Ah, I lost my contributor badge! 😔 Maybe it's because my old Chef work email is no longer tied to this account or something |
This was referenced Oct 11, 2023
@ahasunos nice! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Version:
Train 3.10.8
Environment:
MacOS Sonoma, InSpec 5.22.3, Ruby 3.1.4
InSpec installed and managed via Bundler:
Scenario:
Run a basic profile. I'm seeing the issue against a Kubernetes target, but I don't believe the issue is specific to train-kubernetes, but rather the version of ActiveSupport that Train is using.
I believe it can be resolved by tweaking the dependency version to something like
~> 7.0.0
instead of>= 6.0.3.1
. There's some discussion in inspec/inspec#6527Steps to Reproduce:
Use the Gemfile mentioned above, and a similar
inspec.yml
for a profile:Run InSpec:
Expected Result:
InSpec runs as expected.
Actual Result:
The text was updated successfully, but these errors were encountered: