[chef] Re: Re: Re: Berkshelf with chef-repo: am I doing it right?

[Vladimir Skubriev < >]

02.12.2013 23:09, Joshua Timberman пишет:
> I wrote a blog post awhile back[1] about my own personal chef-repo
> conversion to use Berkshelf. The information is not all still 100%
> relevant/accurate given the entropy of tool development and my
> personal use patterns, but it's pretty close.
>
> I still have a ./cookbooks directory, because I don't see a reason to
> publish and manage 20+ additional cookbook repositories, especially
> private ones. The main difference between the post and now is have a
> helper method like this in the Berksfile:
>
> def internal_cookbook(name, version = '>= 0.0.0', options = {})
>    cookbook name, version, { :path => "./cookbooks/#{name}" }.merge(options)
> end
>
> Then for all the "internal" cookbooks, in the ./cookbooks directory, I
> have entries like this:
>
> internal_cookbook "housepub-workstation"
> internal_cookbook "users"
>
> Internally at Opscode, we're currently doing something like this, too.
> We're working to move to a single-repo-per-cookbook as a longer term
> goal.
>
> Hope this helps,
> Joshua
>
> [1]: 
> http://jtimberman.housepub.org/blog/2012/11/19/chef-repository-berkshelf-conversion/
> - apparently a year ago in fact :).
Okey.

I know that now you switch to using chef-vault. And recommend it to me 
in last mail.

As are you did it before know about chef-vault ?

For example you need to use community mysql cookbook in 
"housepub-cookbook" application cookbook.

If you use mysql cookbook you need to define attribute with a password 
of mysql root, before use of cookbook in application (your's internal 
cookbook) cookbook.

node['mysql']['server_root_password']

Do you define this node attribute in application (internal) cookbook 
"housepub-workstation"

in plaintext | or write a code to extract passwords from databags with 
you preference ?

--
Best regards,

CVision Lab System Administrator
Vladmir Skubriev