{"id":671,"date":"2017-07-26T06:39:53","date_gmt":"2017-07-26T06:39:53","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2017\/07\/26\/what-is-the-significance-of-the-default-directory-under-chef-cookbook-templates\/"},"modified":"2021-11-19T05:56:36","modified_gmt":"2021-11-19T05:56:36","slug":"what-is-the-significance-of-the-default-directory-under-chef-cookbook-templates","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-the-significance-of-the-default-directory-under-chef-cookbook-templates\/","title":{"rendered":"What is the significance of the default directory under chef cookbook \/templates?"},"content":{"rendered":"
<\/div>\n
What is the significance of the default directory under chef cookbook \/templates?<\/div>\n
<\/div>\n
A cookbook is frequently designed to work across many platforms and is often required to distribute a specific template to a specific platform. This is a New in Chef Client 12.0. A cookbook can be designed to support the distribution of templates across platforms, while ensuring that the correct template ends up on each system.<\/div>\n
<\/div>\n
The pattern for template specificity depends on two things: the lookup path and the source. The first pattern that matches is used:<\/strong><\/div>\n
<\/div>\n
\/host-$fqdn\/$source<\/div>\n
\/$platform-$platform_version\/$source<\/div>\n
\/$platform\/$source<\/div>\n
\/default\/$source<\/div>\n
\/$source<\/div>\n
<\/div>\n
Use an array with the source property to define an explicit lookup path. For example:<\/strong><\/div>\n
template ‘\/test’ do<\/div>\n
  source [“#{node.chef_environment}.erb”, ‘default.erb’]<\/div>\n
end<\/div>\n
<\/div>\n
The following example emulates the entire file specificity pattern by defining it as an explicit path:<\/strong><\/div>\n
template ‘\/test’ do<\/div>\n
  source %W{<\/div>\n
    host-#{node[‘fqdn’]}\/test.erb<\/div>\n
    #{node[‘platform’]}-#{node[‘platform_version’]}\/test.erb<\/div>\n
    #{node[‘platform’]}\/test.erb<\/div>\n
    default\/test.erb<\/div>\n
  }<\/div>\n
end<\/div>\n
<\/div>\n
A cookbook may have a \/templates directory structure like this:<\/strong><\/div>\n
\/templates\/<\/div>\n
  windows-6.2<\/div>\n
  windows-6.1<\/div>\n
  windows-6.0<\/div>\n
  windows<\/div>\n
  default<\/div>\n
<\/div>\n
and a resource that looks something like the following:<\/strong><\/div>\n
template ‘C:\\path\\to\\file\\text_file.txt’ do<\/div>\n
  source ‘text_file.txt’<\/div>\n
  mode ‘0755’<\/div>\n
  owner ‘root’<\/div>\n
  group ‘root’<\/div>\n
end<\/div>\n
<\/div>\n
This resource would be matched in the same order as the \/templates directory structure. For a node named host-node-desktop that is running Windows 7, the second item would be the matching item and the location:<\/strong><\/div>\n
\/templates<\/div>\n
  windows-6.2\/text_file.txt<\/div>\n
  windows-6.1\/text_file.txt<\/div>\n
  windows-6.0\/text_file.txt<\/div>\n
  windows\/text_file.txt<\/div>\n
\n

  default\/text_file.txt<\/p>\n

Reference<\/strong>
\nhttps:\/\/docs.chef.io\/resource_template.html<\/a><\/p>\n<\/div>\n\n