9 Commits (abfa35db7ca4386da73645c16ebe2aed3dcbacfe)

Author	SHA1	Message	Date
George Christou	61277c0dbd	website/docs: Run `terraform fmt` on code examples (#12075) ... * docs/vsphere: Fix code block * docs: Convert `...` to `# ...` to allow `terraform fmt`ing * docs: Trim trailing whitespace * docs: First-pass run of `terraform fmt` on code examples	9 years ago
Sean Chittenden	3127998ecd	Remove the AWS Access Key and Secret Access keys from the (#12061) ... `consul_agent_self` data source. Pro tip: update consul! I was using an old branch of Consul, not `origin/master`.	9 years ago
Sean Chittenden	5f3b6ffdb2	Add `consul_agent_self` docs and synchronize a few missing attributes.	9 years ago
Sean Chittenden	e7a8f25388	Push out the last of the docs and fixes for the `consul_catalog_nodes` data source.	9 years ago
Sean Chittenden	1c7a924258	Update and provide docs to the `consul_catalog_service` data source.	9 years ago
Sean Chittenden	9d06a47069	Add docs for the `consul_catalog_services` data source.	9 years ago
James Turnbull	2f61c89c10	Fixed weird cnp	10 years ago
James Turnbull	464d63b890	Minor tidying of the Consul documentation	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