12179 Commits (f4791f0e82b0a95a2685ef28d0dc01bafd7c39de)

 

All Branches   

Search

Author	SHA1	Message	Date
Kenia	7a1284e11b	ui: Redesign - Node service instances tab (#8204) ... * Upgrade consul-api-dobule to version 3.1.3 * Create ConsulInstaceChecks component with test * Redesign: Service Instaces tab in for a Node * Update Node tests to work with the ConsulServiceInstancesList * Style fix to the copy button in the composite-row details * Delete helper and move logic to ConsulInstanceChecks component * Delete unused component consul-node-service-list	4 years ago
Matt Keeler	3f04c4a51b	Update CHANGELOG.md	4 years ago
Matt Keeler	e0f9e4a2d9	Merge pull request #8218 from yurkeen/fix-dns-rcode	4 years ago
André	d06d9ef29e	Update lock.mdx (#8217) ... Remove duplicated `-timeout` value.	4 years ago
Hans Hasselberg	95c027a3ea	Update gopsutil (#8208) ... https://github.com/shirou/gopsutil/pull/895 is merged and fixes our problem. Time to update. Since there is no new version just yet, updating to the sha.	4 years ago
John Cowen	07b49f8887	ui: Ensure routing tab is shown when connect enabled (#8209) ... In https://github.com/hashicorp/consul/pull/8065 we attempted to reduce the amount of times that the UI requests the discovery chain endpoint when connect is disabled on a datacenter. Currently we can only tell if connect is disabled on a datacenter by detecting a 500 error from a connect related endpoint. In the above PR we mistakenly returned from a catch instead of rethrowing the error, which meant that when a none 500 error was caught the discovery chain data would be removed. Whilst at first glance this doens't seem like a big problem due to the endpoint erroring, but we also receive a 0 error when we abort endpoints during blocking queries. This means that in certain cases we can remove cached data for the discovery chain and then delay reloading it via a blocking query. This PR replaces the return with a throw, which means that everything is dealt with correctly via the blocking query error detection/logic.	4 years ago
Yury Evtikhov	10361dd210	DNS: add IsErrQueryNotFound function for easier error evaluation	4 years ago
Yury Evtikhov	8d18422f19	DNS: fix agent returning SERVFAIL where NXDOMAIN should be returned	4 years ago
Yury Evtikhov	3b4ddaaab5	DNS: add test to verify NXDOMAIN is returned when a non-existent domain is queried over RPC	4 years ago
Matt Keeler	6e7acfa618	Add an AutoEncrypt “integration” test ... Also fix a bug where Consul could segfault if TLS was enabled but no client certificate was provided. How no one has reported this as a problem I am not sure.	4 years ago
Matt Keeler	2ddcba00c6	Overwrite agent leaf cert trust domain on the servers	4 years ago
Matt Keeler	19040f1166	Store the Connect CA rate limiter on the server ... This fixes a bug where auto_encrypt was operating without utilizing a common rate limiter.	4 years ago
Matt Keeler	a5a9560bbd	Initialize the agent leaf cert cache result with a state to prevent unnecessary second certificate signing	4 years ago
Matt Keeler	39b567a55a	Fix auto_encrypt IP/DNS SANs ... The initial auto encrypt CSR wasn’t containing the user supplied IP and DNS SANs. This fixes that. Also We were configuring a default :: IP SAN. This should be ::1 instead and was fixed.	4 years ago
Davor Kapsa	b287ebc1fb	clean cli.Run error message (#8191)	4 years ago
Fatih Sarhan	f6eaf74de2	docs: Fix typo on openstack cloud-auto-join	4 years ago
Chris Piraino	ea683ebb6c	cli: Output message on success when writing/deleting entries (#7806) ... This provides a user with a better experience, knowing that the command worked appropriately. The output of the write/delete CLI commands are not going to be used in a bash script, in fact previously a success provided no ouput, so we do not have to worry about spurious text being injected into bash pipelines.	4 years ago
Kevin Pruett	8335a15b34	Merge pull request #8202 from hashicorp/pruett.algolia-index-ci ... Add Algolia indexing to CI	4 years ago
Kevin Pruett	41254a1b74	Add Algolia indexing to CI	4 years ago
John Cowen	73e8face3c	ui: Don't hide TTL check output (#8187) ... We'd assumed that TTL check outputs shouldn't be shown as it seemed like they never had outputs, but they can be submitted with notes, which are then converted into the output. This unhides the output for TTLs and treats them exactly the same as other healthchecks.	4 years ago
Seth Hoenig	95f46eb3ed	api/agent: enable setting SuccessBeforePassing and FailuresBeforeCritical in API (#7949) ... Fixes #7764 Until now these two fields could only be set through on-disk agent configuration. This change adds the fields to the agent API struct definition so that they can be set using the agent HTTP API.	4 years ago
Matt Keeler	85fd8c552f	Merge pull request #8193 from hashicorp/feature/auto-config/suppress-config-warnings	4 years ago
R.B. Boyer	75de960011	update changelog	4 years ago
R.B. Boyer	462f0f37ed	connect: various changes to make namespaces for intentions work more like for other subsystems (#8194) ... Highlights: - add new endpoint to query for intentions by exact match - using this endpoint from the CLI instead of the dump+filter approach - enforcing that OSS can only read/write intentions with a SourceNS or DestinationNS field of "default". - preexisting OSS intentions with now-invalid namespace fields will delete those intentions on initial election or for wildcard namespaces an attempt will be made to downgrade them to "default" unless one exists. - also allow the '-namespace' CLI arg on all of the intention subcommands - update lots of docs	4 years ago
Matt Keeler	be576c9737	Use the DNS and IP SANs from the auto config stanza when set	4 years ago
Matt Keeler	e8b39dd255	Overhaul the auto-config translation ... This fixes some issues around spurious warnings about using enterprise configuration in OSS.	4 years ago
Freddy	10d6e9c458	Split up unused key validation for oss/ent (#8189) ... Split up unused key validation in config entry decode for oss/ent. This is needed so that we can return an informative error in OSS if namespaces are provided.	4 years ago
Daniel Nephin	a891ee8428	Merge pull request #8176 from hashicorp/dnephin/add-linter-unparam-1 ... lint: add unparam linter and fix some of the issues	4 years ago
Freddy	70cf674d72	Merge pull request #8186 from hashicorp/docs-cleanup	4 years ago
Freddy	e10058bc3f	Update website/pages/docs/acl/auth-methods/jwt.mdx ... Co-authored-by: Daniel Nephin <dnephin@hashicorp.com>	4 years ago
Kenia	5dd923ee8b	ui: Support ingress gateways upstreams with multiple addresses (#8185) ... * Upgrade consul-api-double to version 3.1.2 * Display multiple addresses for ingress gateway upstreams	4 years ago
Matt Keeler	7041f69892	Merge pull request #8184 from hashicorp/bugfix/goroutine-leaks	4 years ago
freddygv	166da8f710	Remove remaining beta tags	4 years ago
freddygv	3f01e08ae0	Remove stray instruction	4 years ago
freddygv	98c5eb8868	Add docs for upstream destination's namespace	4 years ago
Chris Piraino	df48db0abd	Merge pull request #7932 from hashicorp/ingress/internal-ui-endpoint-multiple-ports ... Update gateway-services-nodes API endpoint to allow multiple addresses	4 years ago
freddygv	394b1f2e7f	Add tabs to config entry examples	4 years ago
Chris Piraino	f213d3592a	remove obsolete comments about test parallelization	4 years ago
Chris Piraino	b3db907bdf	Update gateway-services-nodes API endpoint to allow multiple addresses ... Previously, we were only returning a single ListenerPort for a single service. However, we actually allow a single service to be serviced over multiple ports, as well as allow users to define what hostnames they expect their services to be contacted over. When no hosts are defined, we return the default ingress domain for any configured DNS domain. To show this in the UI, we modify the gateway-services-nodes API to return a GatewayConfig.Addresses field, which is a list of addresses over which the specific service can be contacted.	4 years ago
Matt Keeler	e9835610f3	Add a test for go routine leaks ... This is in its own separate package so that it will be a separate test binary that runs thus isolating the go runtime from other tests and allowing accurate go routine leak checking. This test would ideally use goleak.VerifyTestMain but that will fail 100% of the time due to some architectural things (blocking queries and net/rpc uncancellability). This test is not comprehensive. We should enable/exercise more features and more cluster configurations. However its a start.	4 years ago
Matt Keeler	29d0cfdd7d	Fix go routine leak in auto encrypt ca roots tracking	4 years ago
Matt Keeler	25a4f3c83b	Allow cancelling blocking queries in response to shutting down.	4 years ago
Rebecca Zanzig	864e7f6ae0	Rearrange k8s connect docs to make space for gateways	4 years ago
John Cowen	9e77922daa	ui: Ensure the tooltip panel chevron isn't hidden by overflow (#8183)	4 years ago
Daniel Nephin	0279bf6fe5	Update TestAgent_GetCoordinate ... The old test case was a very specific regresion test for a case that is no longer possible. Replaced with a new test that checks the default coordinate is returned.	4 years ago
Daniel Nephin	f65e21e6dc	Remove unused return values	4 years ago
Daniel Nephin	010a609912	Fix a bunch of unparam lint issues	4 years ago
Matt Keeler	15e7b3940c	Ensure that retryLoopBackoff can be cancelled ... We needed to pass a cancellable context into the limiter.Wait instead of context.Background. So I made the func take a context instead of a chan as most places were just passing through a Done chan from a context anyways. Fix go routine leak in the gateway locator	4 years ago
Matt Keeler	1093212176	Add test to ensure the StopChannelContext works properly	4 years ago
Matt Keeler	e2cfa93f02	Don’t leak metrics go routines in tests (#8182)	4 years ago