You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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
..
commands	docs(variables): redundant wording	10 years ago
configuration	docs(variables): describe order of evaluation with files	10 years ago
internals	Use HTTPS + www. for links	10 years ago
modules	command: Change module-depth default to -1	10 years ago
plugins	Added a cast to "(*schema.Provider)" in the standard TestProvider function	10 years ago
providers	Treat each consul key as having its own lifecycle	10 years ago
provisioners	Update null_resource.html.markdown	10 years ago
state	docs/remote-state/s3: Fix typo	10 years ago
index.html.markdown	Add meta descriptions to all pages	12 years ago