Tyler Ball

Implement the same order of operations from the fog driver ^^^ in the aws driver. There should be feature parity across drivers, even if the ENV key name is different.

I believe we already fixed this in kitchen-ec2 - we should look there for an example we can copy.

Related: https://github.com/chef/chef-provisioning-aws/issues/254 and https://github.com/chef/chef-provisioning-aws/issues/256

Yeah, I think this is a legit bug. We have some code in kitchen-ec2 that correctly handles this use case - we should look at that.

@christinedraper Unfortunately not :( The `aws_sdk_type` will start with `Aws` instead of `AWS` like in [aws_iam_role](https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/resource/aws_iam_role.rb#L13). So the best way I do it is with a ctrl+f on the code...

I'm guessing this is failing during tagging of the resource. I have https://github.com/chef/chef-provisioning-aws/pull/299 in progress which should fix this

@morfien101 Are you still experiencing this issue with the ChefDK 0.9.0 and the latest version of chef-provisioning / chef-provisioning-aws ? It should be fixed.

Then we need a matrix of Chef versions to test against

Hey @stuszynski! Thanks for getting this PR setup. I have a few pieces of feedback but I think we can work on getting this merged. First, we definitely want to...

``` From 3b80a04c5992b59c568b5a42550e6702a518d566 Mon Sep 17 00:00:00 2001 From: tyler-ball Date: Thu, 2 Mar 2017 12:05:53 -0600 Subject: [PATCH] WIP: tests --- spec/integration/load_balancer_spec.rb | 34 +++++++++++++++++++++++++++++++--- 1 file changed, 31...