galvanize 0.1.2

data/lib/chef-dk/skeletons/code_generator/templates/default/LICENSE.mit.erb

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) <%= year %> <%= copyright_holder %>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/lib/chef-dk/skeletons/code_generator/templates/default/Policyfile.rb.erb

@@ -0,0 +1,25 @@
+# Policyfile.rb - Describe how you want Chef to build your system.
+#
+# For more information on the Policyfile feature, visit
+# https://docs.chef.io/policyfile.html
+
+# A name that describes what the system you're building with Chef does.
+name '<%= policy_name %>'
+
+<% if include_chef_repo_source %>
+# This lets you source cookbooks from your chef-repo.
+default_source :chef_repo, '../'
+
+<% end -%>
+# Where to find external cookbooks:
+default_source :supermarket
+
+# run_list: chef-client will run these recipes in the order specified.
+run_list '<%= policy_run_list %>'
+
+# Specify a custom source for a single cookbook:
+<% if policy_local_cookbook.nil? %>
+# cookbook 'example_cookbook', path: '../cookbooks/example_cookbook'
+<% else %>
+cookbook '<%= cookbook_name %>', path: '.'
+<% end %>

data/lib/chef-dk/skeletons/code_generator/templates/default/README.md.erb

@@ -0,0 +1,4 @@
+# <%= cookbook_name %>
+
+TODO: Enter the cookbook description here.
+

data/lib/chef-dk/skeletons/code_generator/templates/default/build_cookbook/Berksfile.erb

@@ -0,0 +1,7 @@
+source 'https://supermarket.chef.io'
+
+metadata
+
+group :delivery do
+  cookbook 'test', path: './test/fixtures/cookbooks/test'
+end

data/lib/chef-dk/skeletons/code_generator/templates/default/build_cookbook/metadata.rb.erb

@@ -0,0 +1,10 @@
+name 'build_cookbook'
+maintainer '<%= copyright_holder %>'
+maintainer_email '<%= email %>'
+license '<%= license %>'
+version '0.1.0'
+chef_version '>= 13.0'
+<% if build_cookbook_parent_is_cookbook -%>
+
+depends 'delivery-truck'
+<% end -%>

data/lib/chef-dk/skeletons/code_generator/templates/default/build_cookbook/recipe.rb.erb

@@ -0,0 +1,8 @@
+#
+# Cookbook:: build_cookbook
+# Recipe:: <%= @phase %>
+#
+<%= license_description('#') %>
+<% if build_cookbook_parent_is_cookbook -%>
+include_recipe 'delivery-truck::<%= @phase %>'
+<% end -%>

data/lib/chef-dk/skeletons/code_generator/templates/default/gitignore

@@ -0,0 +1,28 @@
+.vagrant
+*~
+*#
+.#*
+\#*#
+.*.sw[a-z]
+*.un~
+
+# Bundler
+Gemfile.lock
+gems.locked
+bin/*
+.bundle/*
+
+# test kitchen
+.kitchen/
+.kitchen.local.yml
+
+# Chef
+Berksfile.lock
+.zero-knife.rb
+Policyfile.lock.json
+
+# Habitat
+results
+
+# HabiChef Policyfiles
+policyfiles/*.lock.json

data/lib/chef-dk/skeletons/code_generator/templates/default/habitat/README.md.erb

@@ -0,0 +1,96 @@
+# <%= cookbook_name %>
+
+Brief description of habichef_skel
+
+## Maintainers
+
+Names of plan maintainers (The Habitat Maintainers humans@habitat.sh is usually sufficient)
+
+## Type of Package
+
+This should state whether the package is a service package or a binary package.
+
+A service package is something that will be run by the Habitat supervisor (i.e. core/postgresql).  A service package must always have a run file or define pkg_svc_run in the plan.sh file.
+
+A binary package is something that packages up a standalone binary, something that does not need to run under the Habitat supervisor (i.e. core/dep). They are often used as dependencies of other packages. Binary packages do not have a run file and do not need to define pkg_svc_run in the plan.sh file.
+
+## Usage
+
+How would a user use this package?  i.e. can a user simply call the package as a dependency of their application?  Or is there more they need to do?
+
+## Bindings
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+How do other services that want to consume this service bind to it?
+
+Checkout [the core/postgresql](https://github.com/habitat-sh/core-plans/tree/master/postgresql) README for a good example of this.
+
+## Topologies
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+What topologies does this plan support?
+
+### Standalone
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+Check out [the Habitat docs on standalone](https://www.habitat.sh/docs/using-habitat/#standalone) for more details on what the standalone topology is and what it does.
+
+If this plan can be used with the standalone topology, how do you do it?
+
+Checkout [the core/postgresql](https://github.com/habitat-sh/core-plans/tree/master/postgresql) README for a good example of this.
+
+### Leader-Follower
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+If this plan can be used with the leader/follower topology, how do you do it?
+
+Check out [the Habitat docs on Leader-Follower](https://www.habitat.sh/docs/using-habitat/#leader-follower-topology) for more details on what the leader-follower topology is and what it does.
+
+Checkout [the core/postgresql](https://github.com/habitat-sh/core-plans/tree/master/postgresql) README for a good example of this (look under the Clustering heading)
+
+## Update Strategies
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+What update strategies would work best for this plan?
+
+Checkout [the update strategy documentation](https://www.habitat.sh/docs/using-habitat/#update-strategy) for information on the strategies Habitat supports.
+
+### Configuration Updates
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+Checkout the [configuration update](https://www.habitat.sh/docs/using-habitat/#configuration-updates) documentation for more information on what configuration updates are and how they are executed.
+
+Link to the plan's default.toml file to list all the configurable values of the plan.
+
+If your plan has configuration values that require a complete rebuild when updated, note those here.
+
+## Scaling
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+(Optional, but recommended)
+
+How would a user scale this service?
+
+Can this service be run in a cluster and/or as high availability?
+
+## Monitoring
+
+*(This is only required for service packages, not [binary wrapper packages](https://www.habitat.sh/docs/best-practices/#binary-wrapper-packages))*
+
+(Optional, but recommended)
+
+How would a user monitor the health of this surface at the application layer?
+
+This is separate from information about Habitat's HTTP API monitoring service.  This section should include some suggestions about how someone could monitor the application or service outside of Habitat - i.e. using something like sumologic, logstash, etc.  It does not need to be prescriptive, but should include some suggestions of where someone might start.
+
+## Notes
+
+(Optional)
+
+Anything that does not fit in the above sections should go here - i.e. how does this fit into a user's development workflow?

data/lib/chef-dk/skeletons/code_generator/templates/default/habitat/default.toml.erb

@@ -0,0 +1,18 @@
+log_level = "warn"
+# All times are in seconds
+interval = "1800"
+splay = "300"
+splay_first_run = "10"
+run_lock_timeout = "30"
+
+[data_collector]
+  enable = false
+#   Set this to true to enable data collection
+#   enable = "true"
+#   uncomment and set to your automate sever URL
+#   server_url = "https://automate.mydomain.com/data-collector/v0"
+#   For instructions on generating tokens refer to: https://automate.chef.io/docs/api-tokens/
+#   token = "anactualtoken="
+
+# Set cookbook specific attributes
+[attributes]

data/lib/chef-dk/skeletons/code_generator/templates/default/habitat/plan.sh.erb

@@ -0,0 +1,16 @@
+if [ -z ${CHEF_POLICYFILE+x} ]; then
+  policy_name="base"
+else
+  policy_name="${CHEF_POLICYFILE}"
+fi
+
+scaffold_policy_name="$policy_name"
+pkg_name="<%= cookbook_name %>-${policy_name}"
+pkg_origin="<%= defined?(hab_origin) ? hab_origin : (ENV['HAB_ORIGIN'] || 'you must specify your origin') %>"
+pkg_version="0.1.0"
+pkg_maintainer="<%= copyright_holder %> <<%= email %>>"
+pkg_description="The Chef $scaffold_policy_name Policy"
+pkg_upstream_url="http://chef.io"
+pkg_scaffolding="core/scaffolding-chef"
+pkg_svc_user="root"
+pkg_svc_group="root"

data/lib/chef-dk/skeletons/code_generator/templates/default/helpers.rb.erb

@@ -0,0 +1,39 @@
+#
+# Chef Documentation
+# https://docs.chef.io/libraries.html
+#
+
+#
+# This module name was auto-generated from the cookbook name. This name is a
+# single word that starts with a capital letter and then continues to use
+# camel-casing throughout the remainder of the name.
+#
+module <%= @cookbook_class_name %>
+  module <%= @helper_class_name %>
+    #
+    # Define the methods that you would like to assist the work you do in recipes,
+    # resources, or templates.
+    #
+    # def my_helper_method
+    #   # help method implementation
+    # end
+  end
+end
+
+#
+# The module you have defined may be extended within the recipe to grant the
+# recipe the helper methods you define.
+#
+# Within your recipe you would write:
+#
+#     extend <%= @cookbook_class_name %>::<%= @helper_class_name %>
+#
+#     my_helper_method
+#
+# You may also add this to a single resource within a recipe:
+#
+#     template '/etc/app.conf' do
+#       extend <%= @cookbook_class_name %>::<%= @helper_class_name %>
+#       variables specific_key: my_helper_method
+#     end
+#

data/lib/chef-dk/skeletons/code_generator/templates/default/inspec_default_test.rb.erb

@@ -0,0 +1,16 @@
+# InSpec test for recipe <%= cookbook_name %>::<%= recipe_name %>
+
+# The InSpec reference, with examples and extensive documentation, can be
+# found at http://inspec.io/docs/reference/resources/
+
+unless os.windows?
+  # This is an example test, replace with your own test.
+  describe user('root'), :skip do
+    it { should exist }
+  end
+end
+
+# This is an example test, replace it with your own test.
+describe port(80), :skip do
+  it { should_not be_listening }
+end

data/lib/chef-dk/skeletons/code_generator/templates/default/kitchen.yml.erb

@@ -0,0 +1,26 @@
+---
+driver:
+  name: vagrant
+
+provisioner:
+  name: chef_zero
+  # You may wish to disable always updating cookbooks in CI or other testing environments.
+  # For example:
+  #   always_update_cookbooks: <%%= !ENV['CI'] %>
+  always_update_cookbooks: true
+
+verifier:
+  name: inspec
+
+platforms:
+  - name: ubuntu-18.04
+  - name: centos-7
+
+suites:
+  - name: default
+    run_list:
+      - recipe[<%= cookbook_name %>::default]
+    verifier:
+      inspec_tests:
+        - test/integration/default
+    attributes:

data/lib/chef-dk/skeletons/code_generator/templates/default/kitchen_dokken.yml.erb

@@ -0,0 +1,31 @@
+---
+driver:
+  name: dokken
+
+provisioner:
+  name: dokken
+
+transport:
+  name: dokken
+
+verifier:
+  name: inspec
+
+platforms:
+  # @see https://github.com/someara/dokken-images
+  # @see https://hub.docker.com/r/dokken/
+  - name: ubuntu-18.04
+    driver:
+      image: dokken/ubuntu-18.04
+  - name: centos-7
+    driver:
+      image: dokken/centos-7
+
+suites:
+  - name: default
+    run_list:
+      - recipe[<%= cookbook_name %>::default]
+    verifier:
+      inspec_tests:
+        - test/integration/default
+    attributes:

data/lib/chef-dk/skeletons/code_generator/templates/default/kitchen_policyfile.yml.erb

@@ -0,0 +1,33 @@
+---
+driver:
+  name: vagrant
+
+## The forwarded_port port feature lets you connect to ports on the VM guest via
+## localhost on the host.
+## see also: https://docs.vagrantup.com/v2/networking/forwarded_ports.html
+
+#  network:
+#    - ["forwarded_port", {guest: 80, host: 8080}]
+
+provisioner:
+  name: chef_zero
+
+## require_chef_omnibus specifies a specific chef version to install. You can
+## also set this to `true` to always use the latest version.
+## see also: https://docs.chef.io/config_yml_kitchen.html
+
+#  require_chef_omnibus: 12.8.1
+
+verifier:
+  name: inspec
+
+platforms:
+  - name: ubuntu-18.04
+  - name: centos-7
+
+suites:
+  - name: default
+    verifier:
+      inspec_tests:
+        - test/integration/default
+    attributes:

data/lib/chef-dk/skeletons/code_generator/templates/default/metadata.rb.erb

@@ -0,0 +1,20 @@
+name '<%= cookbook_name %>'
+maintainer '<%= copyright_holder %>'
+maintainer_email '<%= email %>'
+license '<%= @spdx_license %>'
+description 'Installs/Configures <%= cookbook_name %>'
+long_description 'Installs/Configures <%= cookbook_name %>'
+version '0.1.0'
+chef_version '>= 13.0'
+
+# The `issues_url` points to the location where issues for this cookbook are
+# tracked.  A `View Issues` link will be displayed on this cookbook's page when
+# uploaded to a Supermarket.
+#
+# issues_url 'https://github.com/<insert_org_here>/<%= cookbook_name %>/issues'
+
+# The `source_url` points to the development repository for this cookbook.  A
+# `View Source` link will be displayed on this cookbook's page when uploaded to
+# a Supermarket.
+#
+# source_url 'https://github.com/<insert_org_here>/<%= cookbook_name %>'

data/lib/chef-dk/skeletons/code_generator/templates/default/policyfiles/base.rb.erb

@@ -0,0 +1,30 @@
+# Policyfile.rb - Describe how you want Chef to build your system.
+#
+# For more information on the Policyfile feature, visit
+# https://docs.chef.io/policyfile.html
+
+# A name that describes what the system you're building with Chef does.
+name 'base'
+
+# Where to find external cookbooks:
+default_source :supermarket
+
+# Refer to https://docs.chef.io/config_rb_policyfile.html
+# For exhaustive options.
+#
+# Use an internal SuperMarket
+# default_source :supermarket, 'https://supermarket.mydomain.com' do
+#   Chef::Config.ssl_verify_mode = :verify_none
+# end
+#
+# Specify your chef repo as the preferred source for the Apache cookbook. 
+# default_source :chef_repo, '../' do |s|
+#   s.preferred_for 'ntp'
+# end
+
+# Your Run List
+# run_list [
+#   "<%= cookbook_name %>::default"
+# ]
+
+run_list [ ]