terraform/builtin/providers
Sander van Harmelen b96f373ee9 Fixing some logic issues with the aws-instance resource
1. The schema contained a few fields that where not marked as
`computed`, while they were updated inside the resource.

2. While updating the `volume_size` it was doing so with a `string`,
but in the schema this field is set as `int`.

3. The set func for calculating the hashes for the `block` set items,
also used computed values to calculate the hash. As these values will
not be in the config, but only in the state, this will always show as a
diff. The solution is to only use the fields that aren’t computed in
order to get consistent hashes.

These where all issues before, but weren’t visible as such. All should
be good again now.
2014-12-25 18:21:05 +01:00
..
atlas builtin/providers/atlas: vet fix 2014-12-17 12:28:28 +01:00
aws Fixing some logic issues with the aws-instance resource 2014-12-25 18:21:05 +01:00
cloudflare Removing obsolete struct tags 2014-11-17 18:57:41 +01:00
cloudstack Changing this fixes an Excoscale issue where 'all' is not allowed 2014-12-19 19:14:46 +01:00
consul Making all function names consistent 2014-12-15 15:26:17 +01:00
digitalocean Making all function names consistent 2014-12-15 15:26:17 +01:00
dnsimple Removing obsolete struct tags 2014-11-17 18:58:41 +01:00
google Fixing the acc tests 2014-11-20 14:30:02 +01:00
heroku builtin/providers/heroku: vet fix 2014-12-17 12:58:12 +01:00
mailgun builtin/providers/mailgun: vet fix 2014-12-17 12:59:07 +01:00
null providers/null: null provider 2014-10-04 16:42:43 -07:00