consul/agent/connect/ca
Daniel Nephin 214dcf8d0d ca: use the real FSM operation in tests
Previously we had a couple copies that reproduced the FSM operation.
These copies introduce risk that the test does not accurately match
production.

This PR removes the test versions of the FSM operation, and exports the
real production FSM operation so that it can be used in tests.

The consul provider tests did need to change because of this. Previously
we would return a hardcoded value of 2, but in production this value is
always incremented.
2021-12-08 17:29:44 -05:00
..
common.go Format certificates properly (rfc7468) with a trailing new line (#10411) 2021-06-30 20:48:29 -04:00
mock_Provider.go Ensure that CA initialization does not block leader election. 2021-01-19 15:27:48 -05:00
provider.go ca: split Primary/Secondary Provider 2021-10-10 15:48:02 -04:00
provider_aws.go ca: accept only the cluster ID to SpiffeIDSigningForCluster 2021-11-16 16:57:21 -05:00
provider_aws_test.go plumb thru root cert tll to the aws ca provider (#11449) 2021-11-04 12:19:08 -07:00
provider_consul.go ca: reduce consul provider backend interface a bit 2021-11-25 11:46:06 -05:00
provider_consul_config.go add root_cert_ttl option for consul connect, vault ca providers (#11428) 2021-11-02 11:02:10 -07:00
provider_consul_test.go ca: use the real FSM operation in tests 2021-12-08 17:29:44 -05:00
provider_test.go add root_cert_ttl option for consul connect, vault ca providers (#11428) 2021-11-02 11:02:10 -07:00
provider_vault.go ca: reduce consul provider backend interface a bit 2021-11-25 11:46:06 -05:00
provider_vault_test.go connect: Support auth methods for the vault connect CA provider (#11573) 2021-11-18 13:15:28 -07:00
testing.go ca: use the real FSM operation in tests 2021-12-08 17:29:44 -05:00