VaultOperations and Passivity about spring-vault HOT 3 CLOSED

How to we do it for something like redis?

from spring-vault.

Redis is one of the data stores that requires active client development. The number of clients providing a generic API (invoking a generic command) increases but Redis is still a pain.

VaultTemplate exposes callback methods (within a Session context and without). Both methods accept callback objects that are called with either VaultSession or VaultClient. VaultSession and VaultClient expose methods for HTTP PUT/POST/GET/DELETE interaction and a exchange method (inspired by RestTemplate).

Within a Vault Session

vaultOperations.doWithVault(new SessionCallback<Object>() {
            @Override
            public Object doWithVault(VaultSession session) {

                session.postForEntity()/putForEntity()/...
                return …;
            }
        })

Without a Vault Session

vaultOperations.doWithVault(new ClientCallback<Object>() {
            @Override
            public Object doWithVault(VaultClient client) {

                client.getForEntity()/client.postForEntity()/…
                return …;
            }
        });

from spring-vault.

Closing this question as we're using now RestTemplate so users are able to interact with Vault's HTTP API within a session/outside a session.

from spring-vault.