-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support chef-client < 12.5.1 #30
Comments
@chris-rock this pretty much means not using the new Custom Resources implementation (https://docs.chef.io/custom_resources.html) for the profile and report libraries and going back to the more traditional LWRP. I think it'll open it up to more customers ultimately who haven't updated. |
@jeremymv2 Yes, that is exactly what I am proposing ;-) |
@chris-rock I've got the implementation ready that will work with chef client 11,12; however one big snag.. Inspec gem 0.19.3 doesn't jive well with any chef-client < 12.4.1 !
|
I tried vendoring the inspec gem but I'm not pleased with that as a solution since it installs a total of 35 gems, including some that build native extensions for a total of 27MB:
|
@jeremymv2 we just released a new version of train that should resolve the issue and includes inspec/train#89 |
@chris-rock The more I look at my HWRP implementation, the more it makes me uncomfortable with the idea. Custom resources were invented for a reason; they're just a much more elegant way. I'd vote to scrap this idea and just require chef-client >= 12.5.1 with custom resource support as that will introduce the least amount of tech debt moving forward. |
@jeremymv2 that makes sense. Therefore, our cookbook requires chef-client 12.5.1, latest version is already 12.9.x |
Cookbook version
latest
Chef-client version
< 12.5.1
Platform Details
all
Scenario:
Run the audit cookbook in chef-client < 12.5.1
Steps to Reproduce:
Run the audit cookbook as part of a converge run.
Expected Result:
audit cookbook works fine, even with older versions of the Chef Client
Actual Result:
use_automatic_resource_name
is not supportedThe text was updated successfully, but these errors were encountered: