Phil Frost 27f0873de7 Don't error when reading s3 bucket with no tags ... s3.GetBucketTagging returns an error if there are no tags associated with a bucket. Consequently, any configuration with a tagless s3 bucket would fail with an error, "the TagSet does not exist". Handle that error more appropriately, interpreting it as an empty set of tags.		2015-04-01 08:57:50 -04:00
..
atlas	Move duplicated envDefaultFunc out of each provider and into Schema.	2015-01-16 17:25:39 +00:00
aws	Don't error when reading s3 bucket with no tags	2015-04-01 08:57:50 -04:00
cloudflare	Move duplicated envDefaultFunc out of each provider and into Schema.	2015-01-16 17:25:39 +00:00
cloudstack	Some small fixes, needed to work with bigger templates	2015-03-25 22:48:44 +01:00
consul	Fix comment in consul provider to not mention digitalocean	2015-01-22 12:45:55 -08:00
digitalocean	providers/digitalocean: add dot in GET response	2015-03-26 10:57:46 -07:00
dme	providers/dme: rename dnsmadeeasy package to dme	2015-02-25 15:54:22 -08:00
dnsimple	Move duplicated envDefaultFunc out of each provider and into Schema.	2015-01-16 17:25:39 +00:00
docker	providers/docker: ping docker server on startup	2015-03-28 19:06:48 -07:00
google	Merge pull request #1239 from BashtonLtd/gce_fix_false_bools	2015-03-26 10:20:52 -07:00
heroku	providers/heroku: empty config vars block shouldn't panic [GH-1211]	2015-03-26 09:45:37 -07:00
mailgun	providers/mailgun: fix sending/receiving records	2015-02-18 17:18:19 -06:00
null	providers/null: null provider	2014-10-04 16:42:43 -07:00
openstack	user_data support	2015-03-31 09:54:50 -06:00