16 Commits (e2b6ccad8a755fb9ea1b32fb71eec02216438111)

Author	SHA1	Message	Date
Radek Simko	43de2afde1	docs: Fix misspelled words	10 years ago
John Dittmar	ddc8f21edc	typo consul catalog entry example ... In the consul catalog entry example `name` was specified in the root of the resource rather than the key `node` which is the actual required key-name.	10 years ago
Ryan Uber	ec7fc60d5f	Adds consul_prepared_query resource (#7474) ... * provider/consul: first stab at adding prepared query support * provider/consul: flatten pq resource * provider/consul: implement updates for PQ's * provider/consul: implement PQ delete * provider/consul: add acceptance tests for prepared queries * provider/consul: add template support to PQ's * provider/consul: use substructures to express optional related components for PQs * website: first pass at consul prepared query docs * provider/consul: PQ's support datacenter option and store_token option * provider/consul: remove store_token on PQ's for now * provider/consul: allow specifying a separate stored_token * website: update consul PQ docs * website: add link to consul_prepared_query resource * vendor: update github.com/hashicorp/consul/api * provider/consul: handle 404's when reading prepared queries * provider/consul: prepared query failover dcs is a list * website: update consul PQ example usage * website: re-order arguments for consul prepared queries	10 years ago
stack72	c1d7ae867f	Merge branch 'gh-2087-consul-service-resource' of https://github.com/maxenglander/terraform into maxenglander-gh-2087-consul-service-resource	10 years ago
Martin Atkins	19d0b42911	provider/consul: consul_keys data source (#7678) ... Previously the consul_keys resource did double-duty as both a reader and writer of values from the Consul key/value store, but that made its interface rather confusing and complex, as well as having all of the other general problems associated with read-only resources. Here we split the functionality such that reading is done with the consul_keys data source while writing is done with the consul_keys resource. The old read behavior of the resource is still supported, but it's no longer documented (except as a deprecation note) and will generate deprecation warnings when used. In future it should be possible to simplify the consul_keys resource by removing all of the read support, but that is deferred for now to give users a chance to gracefully migrate to the new data source.	10 years ago
Max Englander	df4c0c82f2	#2087 merge upstream/master	10 years ago
Martin Atkins	d706130a51	consul_key_prefix resource ... This new resource is an alternative to consul_keys that manages all keys under a given prefix, rather than arbitrary single keys across the entire store. The key advantage of this resource over consul_keys is that it is able to detect and delete keys that are added outside of Terraform, whereas consul_keys is only able to detect changes to keys it is explicitly managing.	10 years ago
Max Englander	4fe7db9441	#2087 add docs for consul_node and consul_service	10 years ago
Max Englander	bdf2bbff2e	merge master	10 years ago
Martin Atkins	2e33f5311c	Treat each consul key as having its own lifecycle ... Previously this resource managed the set of keys as a whole rather than the individual keys, and so it was unable to recognize when a particular managed key is removed and delete just that one key from Consul. Here this is addressed by recognizing that each key actually has its own lifecycle, and detecting when individual keys are added and removed without replacing the entire consul_keys instance. Additionally this restores the behavior of updating the "value" attribute on read, but restricts it only to blocks that already had a value so as to avoid the quirkiness seen previously when we updated blocks that were intended to be read-only. Updating the value is important now, because we rely on this to detect and repair discrepancies between values stored in Consul and values given in the configuration. This change produces a change in the handling of the "delete" attribute. Before it was considered only when the entire consul_keys resource was deleted, but now it is considered also when a particular key block is removed from within a resource.	10 years ago
Max Englander	8c8b58400c	consul_catalog_entry docs: remove errant underscore	10 years ago
Max Englander	adda285cae	finish tests and add docs for consul_{agent_service,catalog_entry}	10 years ago
Seth Vargo	073a0f76c5	Add meta descriptions to all pages	12 years ago
Armon Dadgar	269c5be738	provider/Consul: Support Token. Fixes #378	12 years ago
borgified	9667d1fde2	Otherwsie -> Otherwise	12 years ago
Armon Dadgar	615d724aaa	website: Document consul provider	12 years ago