Spring Cloud Vault proksi zavodini application.run dan oldin o'rnating

ConfigData ga kirish uchun bootstrap reyestri ilgagidan foydalaning; bu oddiy ilova binlari paydo bo'lishidan oldin ham sodir bo'lishi mumkin.

Vault ConfigData taqdim etganda, uning birinchi so'rovi oddiy proksi sozlagichi bini mavjud bo'lishidan oldin sodir bo'lishi mumkin. Buning o'rniga so'rov zavodini bootstrap reyestri orqali o'rnating.

Spring Framework 6.1 yoki undan yangiroq stek uchun:

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 mavjud SpringApplication hisoblanadi. Ushbu initsializatorni run ni chaqirishdan oldin qo'shing, Vault URI va autentifikatsiya sozlamalarini saqlab qoling.

ClientFactoryWrapper bu zavodni Vault ning bootstrap infratuzilmasiga ochib beradi; u bog'liq bo'lmagan HTTP mijozlar uchun butun ilova bo'ylab standart qiymat o'rnatmaydi.

Loyihaning mos keladigan Cloud Vault/Boot bog'liqliklar to'plamidan foydalaning. Apache 4 misollarini Spring Framework 6 ning Apache 5 so'rov zavodiga ko'chirib bo'lmaydi.

Proksi manzilini bootstrap dan oldin ham taqdim eting. Ommaviy ochiq Vault serveri uchun, ommaviy proksilarga ruxsat beradigan yo'lda, ilova boshlanishidan oldin HTTP proksilari ro'yxatidan dan HTTP nomzodini tanlang. Agar u faqat Vault da saqlansa, ilova o'sha birinchi Vault so'rovi uchun zarur bo'lgan yo'lni topa olmaydi.

O'xshash maqolalar