Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Spring config import + config server

Open
#690 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, spring
Domain
backend, cloud

Research direction

Reproduce the sample configuration using the spring.config.import entries for Vault and Config Server, with the settings shown in spring.cloud.vault. Compare the imported values with the conflicting values in configserver.yml; done means the expected Vault configuration from the imported Config Server is applied without duplicating the Vault connection settings.

Written by the indexing model from the issue text.

Description

Describe the bug
When I take config from import configserver + vault, is not possible take the spring clouf vault configuration from the imported config server.

Sample
I have this configuration:
spring:
application:
name: app
profiles:
active:
- dev
config:
import:
- "optional:vault://kv/dev/apps/app"
- "optional:configserver:"

(Mandatory put spring.cloud.vault --> I dont know why)
spring.cloud:
vault:
host: vault-active-internal-sanes-seg-vault-pre.apps.ocp01.san.pre.weu1.azure.paas.cloudcenter.corp
port: 80
scheme: https
uri: https://vault-active-internal-sanes-seg-vault-pre.apps.ocp01.san.pre.weu1.azure.paas.cloudcenter.corp

 connection-timeout: 5000
 read-timeout: 15000   
 token: s.qUphJr9wlcs1oGxReFlKQyqY    

If, I have a different configuration in my configserver.yml from vault, this configuration is not taking into account

Dominant language
Java
Stars
291
Forks
152
Avg merge
7h 10m
Merged PRs (30d)
23

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-vault

All issues in spring-cloud/spring-cloud-vault

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.