mirror of https://github.com/status-im/consul.git
24e11b511e
The fallback method would still work but it would get into a state where it would let the certificate expire for 10s before getting a new one. And the new one used the less secure RPC endpoint. This is also a pretty large refactoring of the auto encrypt code. I was going to write some tests around the certificate monitoring but it was going to be impossible to get a TestAgent configured in such a way that I could write a test that ran in less than an hour or two to exercise the functionality. Moving the certificate monitoring into its own package will allow for dependency injection and in particular mocking the cache types to control how it hands back certificates and how long those certificates should live. This will allow for exercising the main loop more than would be possible with it coupled so tightly with the Agent. # Conflicts: # agent/agent.go |
||
|---|---|---|
| .. | ||
| ca | ||
| common_names.go | ||
| common_names_test.go | ||
| csr.go | ||
| generate.go | ||
| generate_test.go | ||
| parsing.go | ||
| sni.go | ||
| sni_test.go | ||
| testing_ca.go | ||
| testing_ca_test.go | ||
| testing_spiffe.go | ||
| uri.go | ||
| uri_agent.go | ||
| uri_agent_test.go | ||
| uri_service.go | ||
| uri_service_oss.go | ||
| uri_service_test.go | ||
| uri_signing.go | ||
| uri_signing_test.go | ||
| uri_test.go | ||