8 Commits

Author	SHA1	Message	Date
Jeff Mitchell	170521481d	Create sdk/ and api/ submodules (#6583)	2019-04-12 17:54:35 -04:00
Calvin Leung Huang	f63bcdf106	Call wg.Add(1) outside of goroutine (#5716)	2018-11-06 16:36:13 -08:00
Jeff Mitchell	2335958260	Update path_tidy_user_id_test.go	2018-07-25 03:37:24 -04:00
Jeff Mitchell	fb94d03b75	Fix race in test	2018-07-25 00:18:32 -04:00
Jeff Mitchell	77e61243d0	Modify approle tidy to validate dangling accessors (#4981)	2018-07-24 14:00:53 -07:00
Jeff Mitchell	0eebc77263	Fix test	2018-07-12 08:29:04 -04:00
Jeff Mitchell	f493d2436e	Add an idle timeout for the server (#4760) ... * Add an idle timeout for the server Because tidy operations can be long-running, this also changes all tidy operations to behave the same operationally (kick off the process, get a warning back, log errors to server log) and makes them all run in a goroutine. This could mean a sort of hard stop if Vault gets sealed because the function won't have the read lock. This should generally be okay (running tidy again should pick back up where it left off), but future work could use cleanup funcs to trigger the functions to stop. * Fix up tidy test * Add deadline to cluster connections and an idle timeout to the cluster server, plus add readheader/read timeout to api server	2018-06-16 18:21:33 -04:00
Vishal Nayak	462caf4c6d	AppRole: Cleanup accessor indexes and dangling accessor indexes (#3924) ... * Cleanup accessor indexes and dangling accessor indexes * Add a test that exercises the accessor cleanup	2018-02-06 15:44:48 -05:00