You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use these mocks to test to mock out the call to the kms client. However, we don't currently have a way to test the kms client in cmd/keyset.go. It's fairly important to test the tool as it's critical to make sure we can use the kms client without any problem when encryption-kms-key-uri is provided. Without the took working properly, we cannot start the recovery signer in a secure way.
Similarly, we don't have a way to exercise the code path when a valid kms key uri is provided here.
The text was updated successfully, but these errors were encountered:
leighmcculloch
changed the title
exp/services/recoverysigner: think about the strategy to test the KMS client
exp/services/recoverysigner: add tests for the KMS client
Jul 11, 2020
We use these mocks to test to mock out the call to the kms client. However, we don't currently have a way to test the kms client in cmd/keyset.go. It's fairly important to test the tool as it's critical to make sure we can use the kms client without any problem when
encryption-kms-key-uri
is provided. Without the took working properly, we cannot start the recovery signer in a secure way.Similarly, we don't have a way to exercise the code path when a valid kms key uri is provided here.
The text was updated successfully, but these errors were encountered: