https://github.com/stavxyz/terraform-chef-policy-provisioner
👩🍳 Policyfile.rb ⏭ Build 🏗 Policy Archive 📦 ⏭ Execute on node. Automatic. Repeatable. No Chef Server Required.
https://github.com/stavxyz/terraform-chef-policy-provisioner
chef policyfile policyfile-archive provisioner terraform
Last synced: about 2 months ago
JSON representation
👩🍳 Policyfile.rb ⏭ Build 🏗 Policy Archive 📦 ⏭ Execute on node. Automatic. Repeatable. No Chef Server Required.
- Host: GitHub
- URL: https://github.com/stavxyz/terraform-chef-policy-provisioner
- Owner: stavxyz
- Created: 2020-07-11T01:07:15.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2021-03-13T03:51:51.000Z (about 4 years ago)
- Last Synced: 2025-02-14T08:13:31.803Z (3 months ago)
- Topics: chef, policyfile, policyfile-archive, provisioner, terraform
- Language: HCL
- Homepage: https://registry.terraform.io/modules/stavxyz/policy-provisioner/chef
- Size: 110 KB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Chef Policy Provisioner Terraform Module
This module allows you to provision/bootstrap any number of nodes with Chef Policyfiles with just a few lines of code, completely automatically. **No Chef Server Required!**
## What you will need
* A [Policyfile](https://docs.chef.io/policyfile/) which contains your desired machine configuration
* A machine (or machines) to provision.
* These could be [DigitalOcean Droplets](https://registry.terraform.io/providers/digitalocean/digitalocean/latest/docs/resources/droplet), EC2 instances, or even a server on your home network
* As long as you are able to authenticate to the server (either via ssh, or password), this module can provision it
That's it!
## System Requirements
* [Chef Workstation](https://docs.chef.io/workstation/)
* On macs, this can be installed with `brew install --cask chef-workstation`
* Terraform >= 0.14
* [`tfenv` is a great way](https://github.com/tfutils/tfenv) to install/manage your `terraform` cli
* On macs, `brew install tfenv`
## Example
Let's say you have a relatively simple [Policyfile](https://docs.chef.io/policyfile) which provisions your machine with mongodb:
```ruby
name 'mongodb'
default_source :supermarket
cookbook 'sc-mongodb', '~> 4.1.0', :supermarket
run_list 'sc-mongodb::default'
```
and you would like to apply this policy to a VM. For this example let's assume use a [DigitalOcean Droplet](https://registry.terraform.io/providers/digitalocean/digitalocean/latest/docs/resources/droplet).
Also, for the sake of this example, let's assume your local private key, `~/.ssh/id_rsa` corresponds to [an ssh key you have added to your DigitalOcean profile](https://www.digitalocean.com/docs/droplets/how-to/add-ssh-keys/to-account/) as "my-ssh-key".
```terraform
resource "digitalocean_droplet" "chef-node" {
image = "ubuntu-18-04-x64"
name = "chef_mongodb_policy_droplet"
region = "nyc2"
size = "s-1vcpu-1gb"
ssh_keys = ["my-ssh-key"]
}
module "policy-provisioner" {
source = "stavxyz/policy-provisioner/chef"
policyfile = "./Policyfile.rb"
connection = {
host = digitalocean_droplet.chef-node.ipv4_address
private_key = "~/.ssh/id_rsa"
}
}
```
Now you are ready to `terraform apply`.
## How does this work? What happens when I run `terraform apply` using this module?
All of the client-side steps are run in an isolated build directory created by this module. First, the chef policy defined by your Policyfile is built using `chef install` (or `chef update` on subsequent runs). This module determines which of those commands to run automatically. One this is complete, a policyfile archive is built from this using `chef export --archive`. This tarball is then pushed to your target machine(s) over ssh to a predetermined path on the target system. By default, this is `/var/chef/policy/