anchor.diff:    # IF you have your own Chef Server, the default validation client name is
     # chef-validator, unless you changed the configuration.
     #
  -  # config.chef.validation_client_name = "ORGNAME-validator"
  +  #   chef.validation_client_name = "ORGNAME-validator"
   end
  
positive.code:   # Share an additional folder to the guest VM. The first argument is
    # an identifier, the second is the path on the guest to mount the
    # folder, and the third is the path on the host to the actual folder.
    # config.vm.share_folder("v-data", "/vagrant_data", "../data")
  
    # Enable provisioning with chef solo, specifying a cookbooks path (relative
    # to this Vagrantfile), and adding some recipes and/or roles.
    #
    # config.vm.provisioner = :chef_solo
    # config.chef.cookbooks_path = "cookbooks"
    # config.chef.add_recipe "mysql"
    # config.chef.add_role "web"
    #
    # You may also specify custom JSON attributes:
    # config.chef.json = { :mysql_password => "foo" }
  
    # Enable provisioning with chef server, specifying the chef server URL,
    # and the path to the validation key (relative to this Vagrantfile).
  
negative.code:   # HTTP instead of HTTPS depending on your configuration. Also change the
    # validation key to validation.pem.
    #
    # config.vm.provision :chef_server do |chef|
    #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
    #   chef.validation_key_path = "ORGNAME-validator.pem"
    # end
    #
    # If you're using the Opscode platform, your validator client is
    # ORGNAME-validator, replacing ORGNAME with your organization name.
  