Added security group tagging
proposal for making orgs a structure with fields instead of just a name field
update error message
Shaving off some unneeded calls, saving CPU cycles

I know it’s very unlikely that a user will notice the difference, but
why range through the list, generate the set and calculate the
hashcode, only to find out that indexMap == nil (e.g. don’t do anything
with the generated hashcode).

As indexMap is only needed when len(parts) > 0, why not only create and
fill it (in one go) when len(parts) > 0?
Update aws-count example with correct github link
providers/google: add external_address; needed for connection
go fmt
consistent spacing
set default host on connection info
provider/consul: Fixing test harness
provider/consul: Change keyword to key from keys
provider/consul: Fixing test DC
provider/consul: Disambiguate between set/get
providers/aws: ELB treats subnets as a set
helper/schema: test case for boolean diffs
providers/consul: fix delete diff
helper/schema: diffing maps that are computed should not result in
change
helper/schema: sets properly take into account the diff
Update CHANGELOG
providers/aws: ELB should treat subest as a set