chef

I write a custom Lightweight resource. But the notifies and only_if is not recognized. Anyone else get this working? I use these in opsworks supplies resources. So I know I am using them correctly. Unfortunately proprietary code, so I can't post the code. Ok. RTFM. Well not really. I did not find this specific issue covered. If you write your own light weight resource and want to be able to use notifies, then use new_resource.updated_by_last_action(false) or new_resource.updated_by_last_action(true) in your resource action code. notifies will then happen (true) or not happen(false). Here is an

I want to specify cookbook paths using chef_solo as a provisioner in Test Kitchen. We are not using Berkshelf or chef_zero at this time. I set cookbooks_path in my .kitchen.yml file, but it seems like the chef_solo provisioner ignores that flag. See stack trace, below. .kitchen.yml --- driver: name: vagrant provisioner: name: chef_solo require_chef_omnibus: 11.8.0 roles_path: '../../roles' data_bags_path: '../../data_bags' environments_path: '../../environments' cookbooks_path: '../cookbooks, ../../site-cookbooks' Stack trace: $ kitchen converge analytics-centos-65 -----> Starting Kitchen (v1

Note this is a copy of a question I asked on ServerFault but was unable to get an answer for. Hoping I can get some feedback here. I am a developer who recently inherited our previous devops person's chef setup. I'm running Chef 10 server and have realized that the nginx cookbook from opscode still uses nginx version 1.2.6. Since there are many security patches that have been released I'd like to move to 1.4.1 and feel that Chef should make this very easy. However it has proven to be nightmarish. My first thought was to simply make the nginx cookbook "custom" and change the default['nginx'][

The Problem When running custom cookbooks on AWS OpsWorks a setup_failed status appears against the instance and the following in the failure log: [2016-03-26T22:53:48+00:00] INFO: Started chef-zero at chefzero://localhost:8889 with repository at /var/chef One version per cookbook data_bags at /var/chef/runs/62832572-cb67-421a-8309-d831140d7b98/data_bags nodes at /var/chef/runs/62832572-cb67-421a-8309-d831140d7b98/nodes [2016-03-26T22:53:48+00:00] INFO: Forking chef instance to converge... [2016-03-26T22:53:48+00:00] INFO: *** Chef 12.7.2 *** [2016-03-26T22:53:48+00:00] INFO: Chef-client pid:

How do you access node.override using chef.json in a Vagrant file? For example, using vagrant-berkshelf , I'm trying to install a particular Maven version based on Custom JSON Data in the Vagrantfile : chef.json = { 'maven' => { 'version' => '3.0.5' } } cookbooks\maven_custom\attributes\default.rb default['maven']['version'] = "3.2.1" cookbooks\maven_custom\recipes\default.rb Chef::Log.info(node['maven']['version']) When I run vagrant provision , the following gets printed out: 3.2.1 Additionally, I tried vagrant reload --provision , yet still saw "3.2.1" print out. I would've expected 3.0.5

On a vagrant box precise64 (ubuntu 12.04) While creating a user resource with Chef, the home directory is not created: My recipe: user "myuser" do supports :manage_home => true shell "/bin/bash" home "/home/myuser" comment "Created by Chef" password "myencryptedpassword" system true provider Chef::Provider::User::Useradd action :create end When I authenticate: $ su - myuser Password: No directory, logging in with HOME=/ Update - The workaround for precise64 (Ubuntu 12.04 64bit) directory "/home/myuser" do owner "myuser" group "myuser" mode 00755 action :create end While system users usually