How to obtain cookbook dependencies from metadata.rb?

Torben_Knerr · January 9, 2013, 9:44pm

Ohai Chefs,

what’s the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I’m not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via method_missing

but this doesn’t feels quite right…

Thanks!
Torben

Torben_Knerr · January 9, 2013, 10:26pm

Background:

First, I want to emulate Berkshelfs 'metadata' keyword inside a librarian
Cheffile.

Then I want to override the location for some of the metadata-defined
cookbook dependencies in the Cheffile (e.g. use github branch rather than
community site)

Has someone done something like this already?

Am 09.01.2013 22:44 schrieb "Torben Knerr" ukio@gmx.de:

Ohai Chefs,

what's the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I'm not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via method_missing

but this doesn't feels quite right...

Thanks!
Torben

Mike · January 9, 2013, 10:31pm

Has someone done something like this already?
Um, berkshelf.

You can probably figure out some of the work from there. But I have no
idea if the Chef cookbook metadata parser will allow for anything
other than a version string following a cookbook name.

Ref: chef/chef/lib/chef/cookbook/metadata.rb at 10-stable · chef/chef · GitHub

-M

On Wed, Jan 9, 2013 at 5:26 PM, Torben Knerr ukio@gmx.de wrote:

Background:

First, I want to emulate Berkshelfs 'metadata' keyword inside a librarian
Cheffile.

Then I want to override the location for some of the metadata-defined
cookbook dependencies in the Cheffile (e.g. use github branch rather than
community site)

Has someone done something like this already?

Am 09.01.2013 22:44 schrieb "Torben Knerr" ukio@gmx.de:

Ohai Chefs,

what's the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I'm not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via method_missing

but this doesn't feels quite right...

Thanks!
Torben

reset · January 9, 2013, 10:47pm

Hey Torben,

If you're familiar with Ruby you should be able to read the Berkshelf source to get an idea of how I implemented the metadata keyword. The Berkshelf code base is pretty friendly and you should feel free to use any of the classes which aren't marked @api private in your own codebase.

Is there a reason you aren't using Berkshelf for this? The use that you are describing is 100% supported and something that I use in my projects everyday. (overriding the locations of the dependencies found in the metadata)

--
Jamie Winsor
@resetexistence

On Wednesday, January 9, 2013 at 2:31 PM, Mike wrote:

Has someone done something like this already?

Um, berkshelf.

You can probably figure out some of the work from there. But I have no
idea if the Chef cookbook metadata parser will allow for anything
other than a version string following a cookbook name.

Ref: chef/chef/lib/chef/cookbook/metadata.rb at 10-stable · chef/chef · GitHub

-M

On Wed, Jan 9, 2013 at 5:26 PM, Torben Knerr <ukio@gmx.de (mailto:ukio@gmx.de)> wrote:

Background:

First, I want to emulate Berkshelfs 'metadata' keyword inside a librarian
Cheffile.

Then I want to override the location for some of the metadata-defined
cookbook dependencies in the Cheffile (e.g. use github branch rather than
community site)

Has someone done something like this already?

Am 09.01.2013 22:44 schrieb "Torben Knerr" <ukio@gmx.de (mailto:ukio@gmx.de)>:

Ohai Chefs,

what's the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I'm not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via method_missing

but this doesn't feels quite right...

Thanks!
Torben

Torben_Knerr · January 9, 2013, 11:12pm

Hey Mike, Jamie,

Thanks for the replies!

The knockout requirement for librarian in my specific case is http_proxy
support.

I would go for Berkshelf just because of 'metadata' otherwise.
Both are great tools, librarian with a focus on simplicity and Berkshelf
supporting more workflow-like stuff. I like both equally, but neither fully
supports my current case

Cheers, Torben

Am 09.01.2013 23:47 schrieb "Jamie Winsor" jamie@vialstudios.com:

Hey Torben,

If you're familiar with Ruby you should be able to read the Berkshelf
source to get an idea of how I implemented the metadata keyword. The
Berkshelf code base is pretty friendly and you should feel free to use any
of the classes which aren't marked @api private in your own codebase.

Is there a reason you aren't using Berkshelf for this? The use that you
are describing is 100% supported and something that I use in my projects
everyday. (overriding the locations of the dependencies found in the
metadata)

--
Jamie Winsor
@resetexistence
reset (Jamie Stormbreaker) · GitHub

On Wednesday, January 9, 2013 at 2:31 PM, Mike wrote:

Has someone done something like this already?

Um, berkshelf.

You can probably figure out some of the work from there. But I have no
idea if the Chef cookbook metadata parser will allow for anything
other than a version string following a cookbook name.

Ref:
chef/chef/lib/chef/cookbook/metadata.rb at 10-stable · chef/chef · GitHub

-M

On Wed, Jan 9, 2013 at 5:26 PM, Torben Knerr ukio@gmx.de wrote:

Background:

First, I want to emulate Berkshelfs 'metadata' keyword inside a librarian
Cheffile.

Then I want to override the location for some of the metadata-defined
cookbook dependencies in the Cheffile (e.g. use github branch rather than
community site)

Has someone done something like this already?

Am 09.01.2013 22:44 schrieb "Torben Knerr" ukio@gmx.de:

Ohai Chefs,

what's the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I'm not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via method_missing

but this doesn't feels quite right...

Thanks!
Torben

Brian_Akins · January 10, 2013, 3:08am

On Jan 9, 2013, at 5:47 PM, Jamie Winsor jamie@vialstudios.com wrote:

Is there a reason you aren't using Berkshelf for this? The use that you are describing is 100% supported and something that I use in my projects everyday. (overriding the locations of the dependencies found in the metadata)

Berkshelf is also pretty easy to extend as well. We wrote some company specific location handler and that was rather painless.

--bakins

Matt_Ray_OPSCODE · January 10, 2013, 3:07pm

Just to back it up a bit, if you really just need the dependencies from the metadata.rb, you can read a file as a Chef::Cookbook::Metadata and call .dependencies() off of it in 3 or 4 lines of code (more with error checking). Here's an example (lines 68-70 and 83)

github.com

mattray/spiceweasel/blob/master/lib/spiceweasel/cookbooks.rb#L68


  end
  Spiceweasel::Log.debug("cookbook: #{name} #{version} #{options}")

  validate_metadata_or_get_knife_commands_wrapper(name, options, version)

  if options
    unless c_names.empty?
      create_command("knife cookbook#{Spiceweasel::Config[:knife_options]} upload #{c_names.join(' ')}")
      c_names = []
    end
    create_command("knife cookbook#{Spiceweasel::Config[:knife_options]} upload #{name} #{options}")
  else
    c_names.push(name)
  end
  delete_command("knife cookbook#{Spiceweasel::Config[:knife_options]} delete #{name} #{version} -a -y")
  @cookbook_list[name] = version # used for validation
end
unless c_names.empty?
  create_command("knife cookbook#{Spiceweasel::Config[:knife_options]} upload #{c_names.join(' ')}")
end
validate_dependencies unless Spiceweasel::Config[:novalidation]

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

From: Torben Knerr [ukio@gmx.de]
Sent: Wednesday, January 09, 2013 5:12 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: Re: Re: How to obtain cookbook dependencies from metadata.rb?

Hey Mike, Jamie,

Thanks for the replies!

The knockout requirement for librarian in my specific case is http_proxy support.

I would go for Berkshelf just because of 'metadata' otherwise.
Both are great tools, librarian with a focus on simplicity and Berkshelf supporting more workflow-like stuff. I like both equally, but neither fully supports my current case

Cheers, Torben

Am 09.01.2013 23:47 schrieb "Jamie Winsor" <jamie@vialstudios.com mailto:jamie@vialstudios.com>:
Hey Torben,

If you're familiar with Ruby you should be able to read the Berkshelf source to get an idea of how I implemented the metadata keyword. The Berkshelf code base is pretty friendly and you should feel free to use any of the classes which aren't marked @api private in your own codebase.

Is there a reason you aren't using Berkshelf for this? The use that you are describing is 100% supported and something that I use in my projects everyday. (overriding the locations of the dependencies found in the metadata)

--
Jamie Winsor
@resetexistence

On Wednesday, January 9, 2013 at 2:31 PM, Mike wrote:

Has someone done something like this already?
Um, berkshelf.

You can probably figure out some of the work from there. But I have no
idea if the Chef cookbook metadata parser will allow for anything
other than a version string following a cookbook name.

Ref: https://github.com/opscode/chef/blob/10-stable/chef/lib/chef/cookbook/metadata.rb#L252-L267

-M

On Wed, Jan 9, 2013 at 5:26 PM, Torben Knerr <ukio@gmx.de mailto:ukio@gmx.de> wrote:
Background:

First, I want to emulate Berkshelfs 'metadata' keyword inside a librarian
Cheffile.

Then I want to override the location for some of the metadata-defined
cookbook dependencies in the Cheffile (e.g. use github branch rather than
community site)

Has someone done something like this already?

Am 09.01.2013 22tel:09.01.2013%2022:44 schrieb "Torben Knerr" <ukio@gmx.de mailto:ukio@gmx.de>:

Ohai Chefs,

what's the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I'm not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via method_missing

but this doesn't feels quite right...

Thanks!
Torben

Torben_Knerr · January 10, 2013, 9:10pm

Hi all, thanks, that helped a lot.

@Matt Ray: I was missing the .from_file bit which came from the mixin,
thanks!

Torben

On Thu, Jan 10, 2013 at 4:07 PM, Matt Ray matt@opscode.com wrote:

Just to back it up a bit, if you really just need the dependencies from
the metadata.rb, you can read a file as a Chef::Cookbook::Metadata and call
.dependencies() off of it in 3 or 4 lines of code (more with error
checking). Here's an example (lines 68-70 and 83)

spiceweasel/lib/spiceweasel/cookbooks.rb at master · mattray/spiceweasel · GitHub

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

From: Torben Knerr [ukio@gmx.de]
Sent: Wednesday, January 09, 2013 5:12 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: Re: Re: How to obtain cookbook dependencies
from metadata.rb?

Hey Mike, Jamie,

Thanks for the replies!

The knockout requirement for librarian in my specific case is http_proxy
support.

I would go for Berkshelf just because of 'metadata' otherwise.
Both are great tools, librarian with a focus on simplicity and Berkshelf
supporting more workflow-like stuff. I like both equally, but neither fully
supports my current case

Cheers, Torben

Am 09.01.2013 23:47 schrieb "Jamie Winsor" jamie@vialstudios.com:

Hey Torben,

If you're familiar with Ruby you should be able to read the Berkshelf
source to get an idea of how I implemented the metadata keyword. The
Berkshelf code base is pretty friendly and you should feel free to use any
of the classes which aren't marked @api private in your own codebase.

Is there a reason you aren't using Berkshelf for this? The use that you
are describing is 100% supported and something that I use in my projects
everyday. (overriding the locations of the dependencies found in the
metadata)

--
Jamie Winsor
@resetexistence
reset (Jamie Stormbreaker) · GitHub

On Wednesday, January 9, 2013 at 2:31 PM, Mike wrote:

Has someone done something like this already?

Um, berkshelf.

You can probably figure out some of the work from there. But I have no
idea if the Chef cookbook metadata parser will allow for anything
other than a version string following a cookbook name.

Ref:
chef/chef/lib/chef/cookbook/metadata.rb at 10-stable · chef/chef · GitHub

-M

On Wed, Jan 9, 2013 at 5:26 PM, Torben Knerr ukio@gmx.de wrote:

Background:

First, I want to emulate Berkshelfs 'metadata' keyword inside a
librarian
Cheffile.

Then I want to override the location for some of the metadata-defined
cookbook dependencies in the Cheffile (e.g. use github branch rather than
community site)

Has someone done something like this already?

Am 09.01.2013 22:44 schrieb "Torben Knerr" ukio@gmx.de:

Ohai Chefs,

what's the easiest way to obtain the cookbook dependencies defined in
metadata.rb (only direct dependencies are required)?

I'm not too firm with the chef internals yet, thus my first idea was to
evaluate metadata.rb and recording the depends calls via
method_missing

but this doesn't feels quite right...

Thanks!
Torben

Topic		Replies	Views
Specify cookbook dependencies in metadata.rb or in Berksfile? Chef Infra (archive)	3	1990	October 18, 2018
Metadata and cookbook names Chef Infra (archive)	5	433	October 22, 2013
Knife cookbook download no metadata.rb? Chef Infra (archive)	1	1046	April 14, 2016
Berkshelf Question: cookbook versioning in metadata vs. berksfile Chef Infra (archive)	1	749	June 13, 2013
Whats the "right" way to use supermarket? Chef Infra (archive)	6	2795	May 12, 2016

How to obtain cookbook dependencies from metadata.rb?

Thanks, Matt Ray Senior Technical Evangelist | Opscode Inc. matt@opscode.com | (512) 731-2218 Twitter, IRC, GitHub: mattray

Related Topics

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray