Shigar da masana'antar wakili ta Spring Cloud Vault kafin application.run

Lokacin da Vault ke bayar da ConfigData, buƙatarsa ta farko na iya faruwa kafin bean na yau da kullum na daidaita wakili ya kasance. Saka masana'antar buƙatun ta hanyar rijistar bootstrap maimakon haka.

Don tarin Spring Framework 6.1 ko sabo:

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 shine SpringApplication da ke akwai. Ƙara wannan mai farawa kafin kiran run, tare da riƙe URI na Vault da saitunan tabbatarwa.

ClientFactoryWrapper yana fallasa wannan masana'anta ga kayan aikin bootstrap na Vault; ba ya saka tsoho na dukan aikace-aikace ga abokan cinikin HTTP marasa alaƙa.

Yi amfani da saitin dogaro na Cloud Vault/Boot mai dacewa na aikin. Ba za a iya kwafin misalan Apache 4 cikin masana'antar buƙatun Apache 5 ta Spring Framework 6 ba.

Sanya adireshin wakili ya kasance samuwa kafin bootstrap kuma. Don uwar garken Vault da ake iya samu ga jama'a a kan hanyar da ke ba da izinin wakilai na jama'a, zaɓi ɗan takarar HTTP daga jerin wakilan HTTP kafin fara aikace-aikacen. Idan an adana shi a cikin Vault kawai, aikace-aikacen ba zai iya gano hanyar da ake buƙata don wannan buƙatar Vault ta farko ba.