Skip to content

Conversation

@peterneyens
Copy link
Contributor

To use the Transit/TransitClient methods we currently need a token, which VaultClient doesn't expose. This forces the usage of the deprecated Vault methods when vault transit functionality is needed.

If we can create a TransitClient from VaultClient the token can be passed under the hood.

Unfortunately this breaks binary compatibility, not sure if we can solve this without breaking compatibility.

payload: CertificateRequest
): F[VaultSecret[CertificateData]]

def transitFor(keyName: transit.KeyName): F[transit.VaultTransitClient[F]]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A way that you may be able to implement this and preserve bincompat is adding something like this:

  private [vault] def loginToken: F[String] = applicative.pure("")

This way the token is only exposed privately, and it has a default implementation that should satisfy bincompat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants