Use the same attribute name that the chef-server-ctl's cookbooks use (addons, not add_ons). Add a notice about addons being premium features and that they require a proper license. Don't include any addons by default, as we don't know the state of licensing that users have; they must opt into this by modifying the attribute in their wrapper/role.
Instead of notifying that the ingredient should reconfigure, we should use the reconfigure action in the default recipe. It's important to note that while this is idempotent, but it is not convergent, and will run every time chef-client runs on the Chef Server. Also add a recipe to create a user and org, and serverspec to test they exist.
This commit refactors the cookbook for Chef Server 12. The README covers the new scope of this cookbook. We’ve attempted to preserve parity in platform support with that of Chef Server 12 itself. * Remove the omnitruck API client library and related attributes * Use packagecloud repository for packages through the chef_server_ingredient resource * Remove the “dev” recipe * Remove the dependency on the git cookbook * Remove the Vagrantfile - we use test-kitchen now * Update the Berksfile accordingly * Add ServerSpec tests Fixes #46, COOK-4691: use IP address as hostname. Fixed merge conflicts: .kitchen.yml recipes/default.rb Added tests for the no-fqdn suite. whitespace, be aligned correctly chef-solo needs dependencies In the README steps for doing the chef-solo run with this cookbook we also need to get the dependencies in place, since we don’t have a depsolver to do this. also update the cloud in the kitchen it's cool when you forget to save all changes use supermarket for all cookbooks in the solo instructions
Solves: default: Downloading: https://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-12.04_provisionerless.box An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again. The requested URL returned error: 404 Not Found