883 Commits (60e54b8a07076f66ce86bf7c86baea41c8baf199)

Author	SHA1	Message	Date
James Phillips	cce0ace53a	Fixes name of new query ACL.	9 years ago
James Phillips	7ebad899da	Adds a new PUT-based TTL check update endpoint.	9 years ago
James Phillips	ef1a588b7a	Merge pull request #1777 from hashicorp/b-port-docfix ... TLS example and correcting error	9 years ago
James Phillips	b92243d8d0	Tweaks the address and advertise docs.	9 years ago
James Phillips	dca480e284	Cleans up the documents.	9 years ago
James Phillips	7d392118d2	Adds a check for users re-submitting the redacted token.	9 years ago
James Phillips	483898abe5	Renames "prepared_query" ACL policy to "query".	9 years ago
James Phillips	b64f19bb08	Adds an upgrade note about the new ACL behavior.	9 years ago
James Phillips	880cd21667	Refactors docs into a more complete state for prepared query ACLs.	9 years ago
James Phillips	67de77482e	Creates new "prepared-query" ACL type and new token capture behavior. ... Prior to this change, prepared queries had the following behavior for ACLs, which will need to change to support templates: 1. A management token, or a token with read access to the service being queried needed to be provided in order to create a prepared query. 2. The token used to create the prepared query was stored with the query in the state store and used to execute the query. 3. A management token, or the token used to create the query needed to be supplied to perform and CRUD operations on an existing prepared query. This was pretty subtle and complicated behavior, and won't work for templates since the service name is computed at execution time. To solve this, we introduce a new "prepared-query" ACL type, where the prefix applies to the query name for static prepared query types and to the prefix for template prepared query types. With this change, the new behavior is: 1. A management token, or a token with "prepared-query" write access to the query name or (soon) the given template prefix is required to do any CRUD operations on a prepared query, or to list prepared queries (the list is filtered by this ACL). 2. You will no longer need a management token to list prepared queries, but you will only be able to see prepared queries that you have access to (you get an empty list instead of permission denied). 3. When listing or getting a query, because it was easy to capture management tokens given the past behavior, this will always blank out the "Token" field (replacing the contents as <hidden>) for all tokens unless a management token is supplied. Going forward, we should discourage people from binding tokens for execution unless strictly necessary. 4. No token will be captured by default when a prepared query is created. If the user wishes to supply an execution token then can pass it in via the "Token" field in the prepared query definition. Otherwise, this field will default to empty. 5. At execution time, we will use the captured token if it exists with the prepared query definition, otherwise we will use the token that's passed in with the request, just like we do for other RPCs (or you can use the agent's configured token for DNS). 6. Prepared queries with no name (accessible only by ID) will not require ACLs to create or modify (execution time will depend on the service ACL configuration). Our argument here is that these are designed to be ephemeral and the IDs are as good as an ACL. Management tokens will be able to list all of these. These changes enable templates, but also enable delegation of authority to manage the prepared query namespace.	9 years ago
Michael Crilly	4c8725ef63	TLS example and correcting error ... The example configuration file omits TLS support in the HTTP API. This is fine, but a second example demonstrating how to enable TLS over the HTTP API is harmless and, in fact, should be default practice. Using the format `ip:port` in the "addresses" block will cause Consul to crash on reload/start. See issue (#1727)[https://github.com/hashicorp/consul/issues/1727#issuecomment-184980751]	9 years ago
Kim Toms	7e8e11aea3	Update leader-election.html.markdown ... Remove duplicate 'leader'	9 years ago
James Phillips	03602779c6	Fixes a typo.	9 years ago
Michael de Jong	b99824330d	Added a reference to Consultant in the Community Tools section.	9 years ago
James Phillips	d2cc2801fa	Merge pull request #1698 from hashicorp/pr-1547-slackpad ... Implements WAN address translation.	9 years ago
James Phillips	590ab94d8d	Adds documentation for WAN address translation.	9 years ago
James Phillips	eb8ee9fce0	Merge pull request #1609 from kevinsimper/patch-1 ... Updating dns forwarding	9 years ago
James Phillips	d2d6b51fe4	Tweaks the telemetry docs.	9 years ago
James Phillips	d60be51f01	Merge pull request #1284 from nbrownus/telemetry ... Option to disable hostnames from telemetry	9 years ago
James Phillips	64ec6d7d73	Adds a warning about DoS-ing the cluster with consul exec.	9 years ago
Seth Vargo	0cb4318b2e	Order	9 years ago
Justin Plock	9f13bba9b2	Add dropwizard-consul to the Community Tools page	9 years ago
Sean Chittenden	fa0d388ef1	Don't assume /bin/bash is installed on all OSes ... Use `/usr/bin/env bash` where appropriate.	9 years ago
Sean Chittenden	7db70cfcb6	Iterate on the DNS forwarding docs ... Specifically: * add Dnsmasq examples for reverse DNS for most of the RFC1918, 5735, and 6598 netblocks. * Highlight some example options for dnsmasq that are probably of interest. * Add a small section on reverse DNS testing * Break out BINDs troubleshooting with Dnsmasq's troubleshooting Not an exhaustive sweep, but should be helpful when introducing consul to new environments.	9 years ago
Nate Brown	43a4f3fe02	Option to disable hostnames from telemetry	9 years ago
Raja Nadar	cd17cdc03d	fixing small typo in json	9 years ago
Jamie Kelly	f444121b13	Edit intro to present Consul instead of Terraform. ... As this is Consul, not Terraform, it makes sense to use Consul in this intro instead of Terraform.	9 years ago
Justin Wilson	1eb780f1b5	Update services.html.markdown	9 years ago
Seth Vargo	40707934d2	Add structured data	9 years ago
Brent Rojas	784f3b1960	Update hashicorp-ecosystem.html.markdown ... Remove slash from link to blog, which was causing 404 error.	9 years ago
Daryl	b2f8ef9f32	Correcting count of checks ... I saw there were 5 checks listed - script, tcp, http, ttl, docker.	9 years ago
James Phillips	84594c36dd	Bumps website version to 0.6.3.	9 years ago
Kevin Simper	72353c5ad3	Updating dns forwarding ... It is not really clear that you only have to do one of the following and not all three.	9 years ago
Seth Vargo	f4e085ec61	Remove old heroku stuff	9 years ago
James Phillips	182628dace	Bumps website version to 0.6.2.	9 years ago
Jon Benson	dcd01d1858	Fix semaphore typo	9 years ago
Seth Vargo	1001fe3d41	Use sync instead of put	9 years ago
Seth Vargo	f5ffa8fb79	Fix broken link	9 years ago
Seth Vargo	b08efe2cd5	Remove bad CSS	9 years ago
Seth Vargo	b84c0583f5	Update middleman	9 years ago
Seth Vargo	3db4e3dccb	Add Atlas deployment scripts	9 years ago
Seth Vargo	2fc7b6c610	Remove Ruby requirement from Gemfile	9 years ago
Seth Vargo	2c32c81338	Merge pull request #1599 from hashicorp/sethvargo/image_optim ... Optimize images	9 years ago
Seth Vargo	4994d9108e	Optimize images	9 years ago
Seth Vargo	cae0ff354a	Use HTTPS + www. where appropriate	9 years ago
captainill	8bd56dd3be	fix consul logo position in safari	9 years ago
captainill	b3087808ab	fix header fonts safari	9 years ago
James Phillips	28ea3dff91	Adds a note about 2X memory provisioning.	9 years ago
James Phillips	891cba3899	Adds a cautionary note about data fitting into RAM.	9 years ago
James Phillips	c2fdce6dd2	Updates middleman-hashicorp version to get new Solaris logo.	9 years ago