Mocking the Stack Configuration and Deployment Attributes on Vagrant

Create a subdirectory of opsworks_cookbooks named printjson and navigate to it.

Initialize and configure Test Kitchen, as described in Example 1: Installing Packages.

Add two subdirectories to printjson: recipes and environments.

Create MyStack as described in Getting Started with Chef 11 Linux Stacks, including deploying SimplePHPApp. If you prefer, you can omit the second PHP App Server instance called for in Step 4: Scale Out MyStack; the examples don't use those attributes.

If you haven't already done so, start the php-app1 instance, and then log in with SSH.

In the terminal window, run the following agent cli command:

sudo opsworks-agent-cli get_json

This command prints the instance's most recent stack configuration and deployment attributes to the terminal window in JSON format.

Copy the JSON to a .json file and save it in a convenient location on your workstation. The details depend on your SSH client. For example, if you are using PuTTY on Windows, you can run the Copy All to Clipboard command, which copies all the text in the terminal window to the Windows clipboard. You can then paste the contents into a .json file and edit the file to remove extraneous text.

Edit MyStack JSON as needed. Stack configuration and deployment attributes are numerous, and cookbooks typically use only a small subset of them. To keep your environment file manageable, you can edit the JSON so that it retains the original structure but contains only the attributes that your cookbooks actually use.

This example uses a heavily edited version of the MyStack JSON that includes just two ['opsworks']['stack'] attributes, ['id] and ['name']. Create an edited version of the MyStack JSON that looks something like the following:

{
  "opsworks": {
    "stack": {
      "name": "MyStack",
      "id": "42dfd151-6766-4f1c-9940-ba79e5220b58",
    },
  },
}

Create an environment file named test.json with the following contents and save it to the cookbook's environments folder.

{
  "default_attributes": {
    "opsworks" : {
      "stack" : {
        "name" : "MyStack",
        "id" : "42dfd151-6766-4f1c-9940-ba79e5220b58"
      }
    }
  },
  "chef_type" : "environment",
  "json_class" : "Chef::Environment"
}

The environment file has the following elements:

Edit .kitchen.yml to define the Test Kitchen environment, as follows.

---
driver:
  name: vagrant

provisioner:
  name: chef_solo
  environments_path: ./environments

platforms:
  - name: ubuntu-12.04

suites:
  - name: printjson 
    provisioner:
      solo_rb:
        environment: test
    run_list:
      - recipe[printjson::default]
    attributes:

You define the environment by adding the following elements to the default .kitchen.yml created by kitchen init.

Create a recipe file named default.rb with the following content and save it to the cookbook's recipes directory.

log "Stack name: #{node['opsworks']['stack']['name']}"
log "Stack id: #{node['opsworks']['stack']['id']}"

This recipe simply logs the two stack configuration and deployment values that you added to the environment. Although the recipe is running locally in Virtual Box, you reference those attributes using the same node syntax that you would if the recipe were running on an AWS OpsWorks Stacks instance.

Run kitchen converge. You should see something like the following log output.

...
Converging 2 resources       
Recipe: printjson::default       
  * log[Stack name: MyStack] action write[2014-07-01T23:14:09+00:00] INFO: Processing log[Stack name: MyStack] action write (printjson::default line 1)       
[2014-07-01T23:14:09+00:00] INFO: Stack name: MyStack       
             
  * log[Stack id: 42dfd151-6766-4f1c-9940-ba79e5220b58] action write[2014-07-01T23:14:09+00:00] INFO: Processing log[Stack id: 42dfd151-6766-4f1c-9940-ba79e5220b58] action write (printjson::default line 2)       
[2014-07-01T23:14:09+00:00] INFO: Stack id: 42dfd151-6766-4f1c-9940-ba79e5220b58       
...