Faka i-proxy factory ye-Spring Cloud Vault ngaphambi kwe-application.run

Sebenzisa i-bootstrap registry hook ukufinyelela i-ConfigData, okungenzeka ngaphambi kokuba ama-bean ajwayelekile e-application abekhona.

Lapho i-Vault inikeza i-ConfigData, isicelo sayo sokuqala singenzeka ngaphambi kokuba i-bean ejwayelekile yokulungisa i-proxy ibekhona. Faka i-factory yesicelo nge-bootstrap registry esikhundleni salokho.

Nge-stack ye-Spring Framework 6.1 noma entsha:

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 iwukuthi SpringApplication okhona. Engeza lesi siqalisi ngaphambi kokushaya u-run, ugcine i-URI ye-Vault nezilungiselelo zokuqinisekisa.

ClientFactoryWrapper iveza le factory engxenyeni ye-bootstrap ye-Vault; ayifaki okokuzenzakalela kwalo lonke uhlelo kumaklayenti e-HTTP angahlobene.

Sebenzisa isethi yezinciklelwa ze-Cloud Vault/Boot ezihambisana neprojekthi. Izibonelo ze-Apache 4 azikwazi ukukopishwa ku-factory yezicelo ye-Apache 5 ye-Spring Framework 6.

Yenza ikheli le-proxy litholakale ngaphambi kwe-bootstrap futhi. Ngeseva ye-Vault efinyeleleka emphakathini emzileni ovumela ama-proxy omphakathi, khetha umgadli we-HTTP ku-uhlu lwama-proxy e-HTTP ngaphambi kokuthi uhlelo luqale. Uma igcinwa ku-Vault kuphela, uhlelo alukwazi ukuthola umzila odingekayo kuleso sicelo sokuqala se-Vault.

Izihloko ezihlobene