Marka Vault bixiyo ConfigData, codsigeeda koowaad wuxuu dhici karaa ka hor inta aanay jirin bean caadi ah oo proxy-ga habeynaya. Taa beddelkeeda ku rakib warshada codsiyada iyada oo loo marayo diiwaanka bootstrap.

Xirmo Spring Framework 6.1 ama ka cusub:

import java.net.InetSocketAddress;
import java.net.ProxySelector;
import java.net.http.HttpClient;
import org.springframework.http.client.JdkClientHttpRequestFactory;
import org.springframework.vault.config.AbstractVaultConfiguration
    .ClientFactoryWrapper;

var http = HttpClient.newBuilder()
    .proxy(ProxySelector.of(
        new InetSocketAddress("proxy.example.net", 8080)))
    .build();

application.addBootstrapRegistryInitializer(registry ->
    registry.register(ClientFactoryWrapper.class, context ->
        new ClientFactoryWrapper(
            new JdkClientHttpRequestFactory(http))));

application waa SpringApplication jira. Ku dar bilowgaan ka hor inta aadan wicin run, adigoo haynaya URI-ga Vault iyo dhaqanka xaqiijinta.

ClientFactoryWrapper wuxuu warshadan u bandhigaa kaabayaasha bootstrap ee Vault; ma rakibo mid caadi ah oo codsiga oo dhan ah macaamiisha HTTP ee aan la xiriirin.

Isticmaal isku-dhafka ku habboon ee Cloud Vault/Boot ee mashruuca. Tusaalooyinka Apache 4 laguma koobi karo warshada codsiyada Apache 5 ee Spring Framework 6.

Samee cinwaanka proxy-ga mid la heli karo ka hor bootstrap sidoo kale. Server Vault si guud loo gaari karo oo ku yaal waddo ogolaata proxy-yada guud, dooro musharax HTTP ah liiska proxy-yada HTTP ka hor inta aan codsigu bilaaban. Haddii kaliya lagu kaydiyo Vault, codsigu ma heli karo waddada loo baahan yahay codsigii ugu horreeyay ee Vault.

Maqaallo la xiriira