spring-cloud / spring-cloud/spring-cloud-config

Any plan for supporting Azure Key Vault as a backend in Spring Cloud Config Server?

Open
#2,645 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Java
Stars
2k
Forks
1.3k
Avg merge
2d 59m
Merged PRs (30d)
16

Description

Is your feature request related to a problem? Please describe.
This is not directly tied to a problem but rather a feature request to enhance Spring Cloud Config Server. Currently, Azure Key Vault is not natively supported as a backend, which could simplify configuration management in Azure-based environments.

Describe the solution you'd like
I would like Spring Cloud Config Server to natively support Azure Key Vault as a backend, enabling it to fetch configuration properties directly and securely without requiring custom implementations.

Describe alternatives you've considered
Writing a custom EnvironmentRepository to integrate with Azure Key Vault.

Contributor guide

Open the 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.

Research direction

Start by reviewing Spring Cloud Config Server's EnvironmentRepository extension point and Azure Key Vault integration requirements. Define how a native backend would fetch configuration properties securely and what configuration and tests are needed; done means Azure Key Vault can be used directly without a custom EnvironmentRepository.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, java, spring, spring-boot
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.