Databases
StackOverflow2013
Postsdbo
POProgrammatically get Vagrant property in Chef solo recipe
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProgrammatically get Vagrant property in Chef solo recipe
    primarykey
    data
    text
    <p>I have a Chef (solo) recipe which generates a CSS file and puts it somewhere into web root directory (<code>/vagrant/css</code> on VM in my case). The problem is that the recipe needs to know an absolute path to vagrant synced directory on VM - it is a folder where <code>Vagrantfile</code> is, and by default it maps to <code>/vagrant</code> inside a VM.</p> <p>I know <a href="http://docs.vagrantup.com/v2/synced-folders/basic_usage.html" rel="nofollow">how to set that path</a>:</p> <pre class="lang-ruby prettyprint-override"><code>Vagrant.configure("2") do |config| config.vm.synced_folder ".", "/synced/dir/on/vm" end </code></pre> <p>But the problem is how to let the recipe know that <code>/synced/dir/on/vm</code>.</p> <p>Currently I use that:</p> <pre class="lang-ruby prettyprint-override"><code>Vagrant.configure("2") do |config| config.vm.provision :chef_solo do |chef| chef.json = { "base_directory" =&gt; "/vagrant" # THIS IS IT } end end </code></pre> <p>It lets me use <code>node["base_directory"]</code> inside the recipe code, but there is a downside to that: if I was to write multiple recipes, it would be inconvinient to use <code>node["base_directory"]</code> in every recipe. It is much better that hardcoding the path, but it forces me to use same key on <code>chef.json</code> for every recipe.</p> <p>Furthermore, if I'd wish to share my recipe, I would force users to use that <code>"base_directory" =&gt; "/vagrant"</code> key/value pair in their <code>Vagrantfile</code>.</p> <p><strong>Is there an API method to get this synched directory path on VM in the recipe code?</strong> Or more genarally: is there a way to get Vagrant-specific properties from Chef recipes?</p> <p>I scoured Vagrant docs, but there seems to be just a <a href="http://docs.vagrantup.com/v2/synced-folders/basic_usage.html" rel="nofollow">single page on that topic</a>, and because it is specific to Vagrant, there is no related information in <a href="http://docs.opscode.com/" rel="nofollow">Chef docs</a> either.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USscriptin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProgrammatically get Vagrant property in Chef solo recipe
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POProgrammatically get Vagrant property in Chef solo recipe
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would love to know this too. It looks like there used to be some method of doing this, but it doesn't work anymore: https://github.com/aespinosa/workstation-vagrant/blob/master/site-cookbooks/workstation/attributes/default.rb#L23 and https://github.com/xforty/chef-drupal/blob/master/recipes/default.rb#L31
      singulars
      1. POProgrammatically get Vagrant property in Chef solo recipe
      1. USalanthing
    2. COIt's not really clear why you are putting the file generated on the VM back into a folder that is mounted from the host computer. If you just need to drop the file in a 'known' location, maybe use the Chef::Config[:file_cache_path].
      singulars
      1. POProgrammatically get Vagrant property in Chef solo recipe
      1. USCAB
    3. COAnother thought; if other recipes need to know where that specific CSS file ends up, add an attribute to the css recipe, like default[:cssrecipe][:cssdir] = "". In the Vagrantfile json attributes do this; chef.json = { :cssrecipe => { :cssdir => [ "/vagrant" ] }}. In the other recipes' attribute files do this; include_attribute "cssrecipe". within those recipes you can now use node[:cssrecipe][:cssdir]. This is no less burdensome on needing to use chef.json in each Vagrantfile, but it makes the relationship between recipes much more understandable.
      singulars
      1. POProgrammatically get Vagrant property in Chef solo recipe
      1. USCAB
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload