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
Fixed typo

The wrong form of "its" was used. Changed to possessive pronoun instead of contracted verb.
Merge pull request #458 from bengesoff/patch-1

Fixed typo
helper/schema: validate string/bool types [GH-460]
helper/schema: validate maps properly [GH-461]
Merge pull request #433 from jpluscplusm/patch-1

Website: Update aws-count example intro page with correct github link
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