Syntax error in definitions files about chef-postgresql HOT 7 CLOSED

@joeypdx what version of Ruby and Chef are you using? This is currently working for me with the latest omnibus Chef install and chef-solo with Vagrant. This cookbook requires Ruby 1.9, 1.8 won't work. I will update the README with a note that reflects this.

from chef-postgresql.

I also get this error using Ruby 1.9.

from chef-postgresql.

@dvfabbri thanks for the report. What version of Chef and what version of Ruby are you using? I did update the syntax from 1.8-style to 1.9-style hashes between 0.11.3 and 0.12.0 of this cookbook, but I am currently using this in production in several places with Chef 11.4.4 and 11.6.0 via Ruby 1.9.3 without issue.

Let me know, I'd like to help you debug this issue. Thanks.

from chef-postgresql.

Chef 10.14.2 and ruby 1.9.3. Perhaps I need to update chef. I am just using
what was packaged with the latest download of vagrant.

On Thu, Sep 26, 2013 at 11:31 PM, Phil Cohen [email protected]:

@dvfabbri https://github.com/dvfabbri thanks for the report. What
version of Chef and what version of Ruby are you using? I did update the
syntax from 1.8-style to 1.9-style hashes between 0.11.3 and 0.12.0 of this
cookbook, but I am currently using this in production in several places
with Chef 11.4.4 and 11.6.0 via Ruby 1.9.3 without issue.

Let me know, I'd like to help you debug this issue. Thanks.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/49#issuecomment-25222179
.

from chef-postgresql.

@dvfabbri thanks for the information. I have been using the vagrant-omnibus plugin recently to integrate Chef with Vagrant. My Vagrantfile (using Vagrant 1.2.7) is bootstrapped with the following:

Vagrant.require_plugin("vagrant-omnibus")

Vagrant.configure("2") do |config|
  config.omnibus.chef_version = :latest
  # ...
end

If you get a chance, please give that a try an let me know how it turns out. I'm hoping this issue is just version related. If not, I'm happy to work to get it resolved. Thanks for your time and patience!

from chef-postgresql.

So I unfortunately ran into this today using opsworks, and have come to find out that they bootstrap (and only support) with 1.8.7. So for now, I've forked and just reverted the 1.9.3 specific changes.

I'll try and stay in sync with your upstream changes as long as possible ;)

from chef-postgresql.

Saw the same issue with 2c412e2

I have omnibus set to :latest but on vagrant provision was seeing chef 10.14.2 being pulled in for some reason.

Ran vagrant destroy -f && vagrant up, which seems to have fixed the issue.

from chef-postgresql.