chef-cli 1.0.3

data/lib/chef-cli/skeletons/code_generator/files/default/build_cookbook/kitchen.yml

@@ -0,0 +1,21 @@
+---
+driver:
+  name: vagrant
+  synced_folders:
+    - [<%= File.join(ENV['PWD'], '..', '..')%>, '/tmp/repo-data']
+
+provisioner:
+  name: chef_zero
+  encrypted_data_bag_secret_key_path: 'secrets/fakey-mcfakerton'
+  data_bags_path: './data_bags'
+  product_name: chefdk
+
+platforms:
+  - name: ubuntu-18.04
+  - name: centos-7
+
+suites:
+  - name: default
+    run_list:
+      - recipe[test]
+    attributes:

data/lib/chef-cli/skeletons/code_generator/files/default/build_cookbook/test-fixture-recipe.rb

@@ -0,0 +1,8 @@
+%w(unit lint syntax).each do |phase|
+  # TODO: This works on Linux/Unix. Not Windows.
+  execute "HOME=/home/vagrant delivery job verify #{phase} --server localhost --ent test --org kitchen" do
+    cwd '/tmp/repo-data'
+    user 'vagrant'
+    environment('GIT_DISCOVERY_ACROSS_FILESYSTEM' => '1')
+  end
+end

data/lib/chef-cli/skeletons/code_generator/files/default/chefignore

@@ -0,0 +1,110 @@
+# Put files/directories that should be ignored in this file when uploading
+# to a Chef Infra Server or Supermarket.
+# Lines that start with '# ' are comments.
+
+# OS generated files #
+######################
+.DS_Store
+ehthumbs.db
+Icon?
+nohup.out
+Thumbs.db
+
+# SASS #
+########
+.sass-cache
+
+# EDITORS #
+###########
+.#*
+.project
+.settings
+*_flymake
+*_flymake.*
+*.bak
+*.sw[a-z]
+*.tmproj
+*~
+\#*
+mkmf.log
+REVISION
+TAGS*
+tmtags
+
+## COMPILED ##
+##############
+*.class
+*.com
+*.dll
+*.exe
+*.o
+*.pyc
+*.so
+*/rdoc/
+a.out
+
+# Testing #
+###########
+.circleci/*
+.codeclimate.yml
+.foodcritic
+.kitchen*
+.rspec
+.rubocop.yml
+.travis.yml
+.watchr
+azure-pipelines.yml
+examples/*
+features/*
+Guardfile
+kitchen.yml*
+Procfile
+Rakefile
+spec/*
+spec/*
+spec/fixtures/*
+test/*
+
+# SCM #
+#######
+.git
+.gitattributes
+.gitconfig
+.github/*
+.gitignore
+.gitmodules
+.svn
+*/.bzr/*
+*/.git
+*/.hg/*
+*/.svn/*
+
+# Berkshelf #
+#############
+Berksfile
+Berksfile.lock
+cookbooks/*
+tmp
+
+# Bundler #
+###########
+vendor/*
+Gemfile
+Gemfile.lock
+
+# Policyfile #
+##############
+Policyfile.rb
+Policyfile.lock.json
+
+# Cookbooks #
+#############
+CHANGELOG*
+CONTRIBUTING*
+TESTING*
+CODE_OF_CONDUCT*
+
+# Vagrant #
+###########
+.vagrant
+Vagrantfile

data/lib/chef-cli/skeletons/code_generator/files/default/cookbook_readmes/README-policy.md

@@ -0,0 +1,9 @@
+This directory typically contains Chef cookbooks. This repository was
+generated with the '--policy-only' option, which means you have chosen
+to use a workflow where each cookbook is treated as an independent
+software project. As a result, any cookbooks present in this directory
+are independent git projects, and the contents of this directory have
+been added to .gitignore.
+
+Love,
+Chef

data/lib/chef-cli/skeletons/code_generator/files/default/cookbook_readmes/README.md

@@ -0,0 +1,66 @@
+This directory contains the cookbooks used to configure systems in your infrastructure with Chef - an example basic cookbook called `example` has been automatically created for you.
+
+Knife needs to be configured to know where the cookbooks are located with the `cookbook_path` setting. If this is not set, then several cookbook operations will fail to work properly.
+
+```
+cookbook_path ["./cookbooks"]
+```
+
+This setting tells knife to look for the cookbooks directory in the present working directory. This means the knife cookbook subcommands need to be run in the `chef-repo` directory itself. To make sure that the cookbooks can be found elsewhere inside the repository, use an absolute path. This is a Ruby file, so something like the following can be used:
+
+```
+current_dir = File.dirname(__FILE__)
+cookbook_path ["#{current_dir}/../cookbooks"]
+```
+
+Which will set `current_dir` to the location of the config.rb (previously knife.rb) file itself (e.g. `~/chef-repo/.chef/config.rb`).
+
+Configure knife to use your preferred copyright holder, email contact and license. Add the following lines to `.chef/config.rb`.
+
+```
+cookbook_copyright "Example, Com."
+cookbook_email     "cookbooks@example.com"
+cookbook_license   "apachev2"
+```
+
+Supported values for `cookbook_license` are "apachev2", "mit","gplv2","gplv3", or "none". These settings are used to prefill comments in the default recipe, and the corresponding values in the metadata.rb. You are free to change the the comments in those files.
+
+Create new cookbooks in this directory with Chef.
+
+```
+chef generate cookbook COOKBOOK
+```
+
+This will create all the cookbook directory components. You don't need to use them all, and can delete the ones you don't need. It also creates a README file, metadata.rb and default recipe.
+
+You can also download cookbooks directly from the Chef Supermarket site. There are two subcommands to help with this depending on what your preference is.
+
+The first and recommended method is to use a vendor branch if you're using Git. This is automatically handled with Knife.
+
+```
+knife cookbook site install COOKBOOK
+```
+
+This will:
+
+- Download the cookbook tarball from the Chef Supermarket.
+- Ensure its on the git master branch.
+- Checks for an existing vendor branch, and creates if it doesn't.
+- Checks out the vendor branch (chef-vendor-COOKBOOK).
+- Removes the existing (old) version.
+- Untars the cookbook tarball it downloaded in the first step.
+- Adds the cookbook files to the git index and commits.
+- Creates a tag for the version downloaded.
+- Checks out the master branch again.
+- Merges the cookbook into master.
+- Repeats the above for all the cookbooks dependencies, downloading them from the community site
+
+The last step will ensure that any local changes or modifications you have made to the cookbook are preserved, so you can keep your changes through upstream updates.
+
+If you're not using Git, use the site download subcommand to download the tarball.
+
+```
+knife cookbook site download COOKBOOK
+```
+
+This creates the COOKBOOK.tar.gz from in the current directory (e.g., `~/chef-repo`). We recommend following a workflow similar to the above for your version control tool.

data/lib/chef-cli/skeletons/code_generator/files/default/delivery-config.json

@@ -0,0 +1,17 @@
+{
+  "version": "2",
+  "build_cookbook": {
+    "name": "build_cookbook",
+    "path": ".delivery/build_cookbook"
+  },
+  "delivery-truck": {
+    "lint": {
+      "enable_cookstyle": true
+    }
+  },
+  "skip_phases": [],
+  "job_dispatch": {
+    "version": "v2"
+  },
+  "dependencies": []
+}

data/lib/chef-cli/skeletons/code_generator/files/default/delivery-project.toml

@@ -0,0 +1,34 @@
+# Delivery for Local Phases Execution
+#
+# This file allows you to execute test phases locally on a workstation or
+# in a CI pipeline. The delivery-cli will read this file and execute the
+# command(s) that are configured for each phase. You can customize them
+# by just modifying the phase key on this file.
+#
+# By default these phases are configured for Cookbook Workflow only
+#
+
+[local_phases]
+unit = "chef exec rspec spec/"
+lint = "chef exec cookstyle"
+# Foodcritic includes rules only appropriate for community cookbooks
+# uploaded to Supermarket. We turn off any rules tagged "supermarket"
+# by default. If you plan to share this cookbook you should remove
+# '-t ~supermarket' below to enable supermarket rules.
+syntax = "chef exec foodcritic . -t ~supermarket"
+provision = "chef exec kitchen create"
+deploy = "chef exec kitchen converge"
+smoke = "chef exec kitchen verify"
+# The functional phase is optional, you can define it by uncommenting
+# the line below and running the command: `delivery local functional`
+# functional = ""
+cleanup = "chef exec kitchen destroy"
+
+# Remote project.toml file
+#
+# Instead of the local phases above, you may specify a remote URI location for
+# the `project.toml` file. This is useful for teams that wish to centrally
+# manage the behavior of the `delivery local` command across many different
+# projects.
+#
+# remote_file = "https://url/project.toml"

data/lib/chef-cli/skeletons/code_generator/files/default/gitignore

@@ -0,0 +1,22 @@
+.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

data/lib/chef-cli/skeletons/code_generator/files/default/repo/README.md

@@ -0,0 +1,20 @@
+# Overview
+
+Every Chef Infra installation needs a Chef Repository. This is the place where cookbooks, policyfiles, config files and other artifacts for managing systems with Chef Infra will live. We strongly recommend storing this repository in a version control system such as Git and treating it like source code.
+
+# Repository Directories
+
+This repository contains several directories, and each directory contains a README file that describes what it is for in greater detail, and how to use it for managing your systems with Chef.
+
+- `cookbooks/` - Cookbooks you download or create.
+- `data_bags/` - Store data bags and items in .json in the repository.
+- `roles/` - Store roles in .rb or .json in the repository.
+- `environments/` - Store environments in .rb or .json in the repository.
+
+# Configuration
+
+The config file, `.chef/config.rb` is a repository-specific configuration file for the knife command line tool. If you're using the Hosted Chef platform, you can download one for your organization from the management console. You can also generate a new config.rb by running `knife configure`. For more information about configuring Knife, see the Knife documentation at https://docs.chef.io/knife.html
+
+# Next Steps
+
+Read the README file in each of the subdirectories for more information about what goes in those directories.

data/lib/chef-cli/skeletons/code_generator/files/default/repo/cookbooks/example/README.md

@@ -0,0 +1,27 @@
+# Example
+
+An example cookbook
+
+## Requirements
+
+### Platforms:
+
+_No platforms defined_
+
+### Cookbooks:
+
+_No dependencies defined_
+
+## Attributes
+
+- `node['example']['name']` - Defaults to `Sam Doe`.
+
+## Recipes
+
+- example::default
+
+## License and Maintainer
+
+Maintainer:: (<>)
+
+License:: All rights reserved

data/lib/chef-cli/skeletons/code_generator/files/default/repo/cookbooks/example/attributes/default.rb

@@ -0,0 +1,7 @@
+# This is a Chef Infra Client attributes file. It can be used to specify default
+# and override attributes to be applied to nodes that run this cookbook.
+
+# Set a default name
+default['example']['name'] = 'Sam Doe'
+
+# For further information, see the Chef documentation (https://docs.chef.io/attributes.html).

data/lib/chef-cli/skeletons/code_generator/files/default/repo/cookbooks/example/metadata.rb

@@ -0,0 +1,6 @@
+name 'example'
+description 'An example cookbook'
+maintainer 'Example maintainer'
+maintainer_email 'maintainer@example.com'
+license 'Apache-2.0'
+version '1.0.0'

data/lib/chef-cli/skeletons/code_generator/files/default/repo/cookbooks/example/recipes/default.rb

@@ -0,0 +1,8 @@
+# This is a Chef Infra Client recipe file. It can be used to specify resources
+# which will apply configuration to a server.
+
+log "Welcome to Chef Infra Client, #{node['example']['name']}!" do
+  level :info
+end
+
+# For more information, see the documentation: https://docs.chef.io/recipes.html

data/lib/chef-cli/skeletons/code_generator/files/default/repo/data_bags/README.md

@@ -0,0 +1,56 @@
+# Data Bags
+
+This directory contains directories of the various data bags you create for your infrastructure. Each subdirectory corresponds to a data bag on the Chef Infra Server, and contains JSON files of the items that go in the bag.
+
+For example, in this directory, you'll find an example data bag directory called `example`, which contains an item definition called `example_item.json`
+
+Before uploading this item to the server, we must first create the data bag on the Chef Infra Server.
+
+    knife data bag create example
+
+Then we can upload the items in the data bag's directory to the Chef Infra Server.
+
+    knife data bag from file example example_item.json
+
+For more information on data bags, see the Chef docs site:
+
+https://docs.chef.io/data_bags.html
+
+# Encrypted Data Bags
+
+Encrypted data bags allow you to encrypt the contents of your data bags. The content of attributes will no longer be searchable. To use encrypted data bags, first you must have or create a secret key.
+
+    openssl rand -base64 512 > secret_key
+
+You may use this secret_key to add items to a data bag during a create.
+
+    knife data bag create --secret-file secret_key passwords mysql
+
+You may also use it when adding ITEMs from files,
+
+    knife data bag create passwords
+    knife data bag from file passwords data_bags/passwords/mysql.json --secret-file secret_key
+
+The JSON for the ITEM must contain a key named "id" with a value equal to "ITEM" and the contents will be encrypted when uploaded. For example,
+
+    {
+      "id": "mysql",
+      "password": "abc123"
+    }
+
+Without the secret_key, the contents are encrypted.
+
+    knife data bag show passwords mysql
+    id:        mysql
+    password:  2I0XUUve1TXEojEyeGsjhw==
+
+Use the secret_key to view the contents.
+
+    knife data bag show passwords mysql --secret-file secret_key
+    id:        mysql
+    password:  abc123
+
+
+For more information on encrypted data bags, see the Chef docs site:
+
+https://docs.chef.io/data_bags.html

data/lib/chef-cli/skeletons/code_generator/files/default/repo/data_bags/example/example_item.json

@@ -0,0 +1,4 @@
+{
+    "id": "example_item",
+    "key": "value"
+}

data/lib/chef-cli/skeletons/code_generator/files/default/repo/dot-chef-repo.txt

@@ -0,0 +1,6 @@
+.chef-repo.txt
+==============
+
+This file gives the Chef CLI's generators a hint that you are using a Chef Infra
+Repo and this is the root directory of your Chef Infra Repo. Chef CLI's generators
+use this to generate code that is designed to work with the Chef Repo workflow.