terraform/builtin/providers/consul
Paul Hinze 069425a700 consul: Fix several problems w/ consul_keys update
Implementation notes:

 * The hash implementation was not considering key value, causing "diffs
   did not match" errors when a value was updated. Switching to default
   HashResource implementation fixes this
 * Using HashResource as a default exposed a bug in helper/schema that
   needed to be fixed so the Set function is picked up properly during
   Read
 * Stop writing back values into the `key` attribute; it triggers extra
   diffs when `default` is used. Computed values all just go into `var`.
 * Includes a state migration to prevent unnecessary diffs based on
   "key" attribute hashcodes changing.

In the tests:

 * Switch from leaning on the public demo Consul instance to requiring a
   CONSUL_HTTP_ADDR variable be set pointing to a `consul agent -dev`
   instance to be used only for testing.
 * Add a test that exposes the updating issues and covers the fixes

Fixes #774
Fixes #1866
Fixes #3023
2016-01-26 14:46:26 -06:00
..
config.go
resource_consul_keys.go consul: Fix several problems w/ consul_keys update 2016-01-26 14:46:26 -06:00
resource_consul_keys_migrate.go consul: Fix several problems w/ consul_keys update 2016-01-26 14:46:26 -06:00
resource_consul_keys_migrate_test.go consul: Fix several problems w/ consul_keys update 2016-01-26 14:46:26 -06:00
resource_consul_keys_test.go consul: Fix several problems w/ consul_keys update 2016-01-26 14:46:26 -06:00
resource_provider.go
resource_provider_test.go consul: Fix several problems w/ consul_keys update 2016-01-26 14:46:26 -06:00