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
Chefspec version 7.3.4 causes failures due to definitions being deprecated #588
Comments
This is fixed on master as we've now moved away from definitions, we're just making the last few steps of making sure it works. If you want to give master a spin instead of 5.2.1 (as of writing this ng the latest on Supermarket), turn you should have some better luck with this. If this doesn't work, or run with your orgs expectations, then I suggest dropping the unit testing and focusing on integration testing for now. Closing as won't fix. |
I filed this issue for two reasons:
|
Yeah, I really hear you on this one. It's been a thorn on my side for 6+ months, rewriting this and getting some of the magic better documented. This milestone is what's left to be written https://github.com/sous-chefs/apache2/milestone/8 I'm currently working on the ssl & website resource as we speak. So if you're OK with no mod_php support, I'm inclined the cut v6 at that point |
Unfortunately, I am leveraging |
Using the chef-client baked into ChefDK is causing issues with the fog-openstack gem since it is locked in ChefDK. To work around this and better mimic how this is used in production, switch the integration tests to installing chef-client instead of ChefDK. - Split out pre-run playbooks between delivery and integration (keep ChefDK for delivery) - Install Chef 14 by default - Install Berkshelf in Chef - Install cookstyle which is needed in the Rakefile - Update command paths so that berkshelf is available with Chef and ChefDK - Update ChefDK to 3.2.30 but not higher due to issues with chefspec and apache2 [1] - Upgrade fog-openstack gem to work around extraneous warnings to match cookbook-openstackclient - Remove unneeded pip downgrade [1] sous-chefs/apache2#588 Change-Id: I0b0c2eb80dc0d831685cc7f69a1186a6148e6258 Signed-off-by: Lance Albertson <lance@osuosl.org>
* Update openstack-chef from branch 'master' - Install and use Chef Client instead of ChefDK on integration tests Using the chef-client baked into ChefDK is causing issues with the fog-openstack gem since it is locked in ChefDK. To work around this and better mimic how this is used in production, switch the integration tests to installing chef-client instead of ChefDK. - Split out pre-run playbooks between delivery and integration (keep ChefDK for delivery) - Install Chef 14 by default - Install Berkshelf in Chef - Install cookstyle which is needed in the Rakefile - Update command paths so that berkshelf is available with Chef and ChefDK - Update ChefDK to 3.2.30 but not higher due to issues with chefspec and apache2 [1] - Upgrade fog-openstack gem to work around extraneous warnings to match cookbook-openstackclient - Remove unneeded pip downgrade [1] sous-chefs/apache2#588 Change-Id: I0b0c2eb80dc0d831685cc7f69a1186a6148e6258 Signed-off-by: Lance Albertson <lance@osuosl.org>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Cookbook version
5.2.1
Chef-client version
chefdk
3.6.57
chef
14.8.12
chefspec
7.3.4
Platform Details
Development OS:
Mac OS 13
Target OS:
CentOS 7
Scenario:
Including
apache2::default
causes unit testing to fail. Period. Integration and deployment still appear to be unaffected.Steps to Reproduce:
Include the
apache2::default
on recipe that has a spec file, run chefspec against it.Expected Result:
Unit testing to proceed as expected.
Actual Result:
Related Chefspec issue: chefspec/chefspec#926
The text was updated successfully, but these errors were encountered: