[chef] Re: Re: Re: Re: Chef Client 12.1.0 Released

[Ranjib Dey < >]

its a single invocation, so it will speed up chef run a lot. Unlike user or directory, generally package installation involves multiple network calls, hence its makes more sense to do this for packages. Also user provider (useradd/usermod etc) does not allow multiple user modification, while package provider (like apt, yum) all supports multiple package installation.

cheers

ranjib

On Sat, Mar 7, 2015 at 4:43 AM, Ameir Abdeldayem < " target="_blank"> > wrote:

Regarding the multi-package support, what benefits does it bring to the table over something like this?:

{"php-pecl-imagick" => "3.1.2-2.el6", "ImageMagick-last-libs" => "6.8.7.4-1.el6", "other-package" => nil}

.each do |package, version|

  package package do

    version version

  end

end

I agree with the others that having to keep track of indices is a poor approach.

Also, most (all?) resources currently apply to a single target (a user account, a directory, a file, etc.).  Will the package resource be the special exception, or will other resources follow suit with the array format?  e.g., will we be seeing things like `directory ["/dir1", "/dir2"]` down the road?

On Fri, Mar 6, 2015 at 1:37 PM, Charles Johnson < " target="_blank"> > wrote:

+1 on this, having people manually keep array indices in sync isn't safe.

I've created https://github.com/chef/chef/issues/3040 to track this.

--Charles

On March 4, 2015 at 10:58:49 AM, Michael Fischer ( " target="_blank"> ) wrote:

I did some background reading on the list support to the package provider.  

While I'm very pleased that you can now do package installations much faster, I'm concerned about the syntax.  In particular, my concern is the way names and versions are mapped using a pair of Arrays instead of a more logical Hash map.  I'd expect something like:

packages "group" do

  list { "foo" => "1.0.0", "bar", => "2.1.7" }

end

Instead we got something like this:

package ["foo", "bar"] do

  version ["1.0.0", "2.1.7"]

end

For reasonably short lists, this is fine, but once you get past 5 or so, having to iterate the lists by hand to match the name and version will become extremely difficult and error prone.  If the above couldn't be done using the package provider, I'd suggest that a new resource should have been created instead so that the semantics could be better defined.

Best regards,

--Michael

On Tue, Mar 3, 2015 at 10:43 AM, Jay Mundrawala < " target="_blank"> > wrote:

Hi Chefs,

We've just released Chef 12.1.0. You can read more about it at https://www.chef.io/blog/2015/03/03/chef-12-1-0-released/.

Thanks,

Jay