dougireton

Per our discussion today we have the following recommendations:

1. Pick a single easy server “role” to automate, e.g. my_web_server.
Get that cookbook installing a single package a single Windows Feature, across all of your environments, including Prod. 

2. Then rapidly iterate on that cookbook adding features and deploying through all environments, including Prod. 
Build a regular habit of code review. Every change should be reviewed by another engineer.
Feel free to include Chef team engineers on Pull Requests.

3. Ideally you start writing simple tests with the cookbook, which our Cookbook Pipeline will execute on every Git push and merge.

dougireton

{
  "chefdk_bootstrap" : {
    "package" : {
      "atom" : false,
      "git" : false,
      "iterm2" : false,
      "vagrant" : false,
      "chefdk_julia" : false
    }
  }

dougireton

# Description: Boxstarter Script
# Author: Jess Frazelle <[email protected]>
# Last Updated: 2017-09-11
#
# Install boxstarter:
# 	. { iwr -useb http://boxstarter.org/bootstrapper.ps1 } | iex; get-boxstarter -Force
#
# You might need to set: Set-ExecutionPolicy RemoteSigned
#
# Run this boxstarter by calling the following from an **elevated** command-prompt:

dougireton

---
AWSTemplateFormatVersion: '2010-09-09'
Description: 'Cloudformation stack to manage permission to deploy a serverless service'

Parameters:
  ServiceName:
    Description: Name of the Service you want to deploy
    Type: String

Resources:

dougireton

#cloud-config
        package_update: true
        package_upgrade: true
        packages:
          - alloy # Grafana Alloy
          - ca-certificates
          - docker.io
          - gnupg
        apt:
          sources: