Feature 2 — Provider-Aware Config & Runtime Selection
Open
Nobody has claimed this yet.
stale
Team : Maintenance
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Outcome:
- Finalize multi-provider config shape based on spike outcome.
- If applies
ProviderTypeenum:OPENAI,AZURE,BEDROCK,VERTEXor what we decided after the spike - Refactor
AppConfig&ConfigServiceto store and load provider-specific settings. - Migration: auto-map legacy OpenAI configs to "OpenAI Official SDK".
- Tests: switching provider toggles correct config, returns valid LangChain4j client.
Why:
- Enables flexible cloud AI choices.
- No hidden breakage for existing keys.
- Foundation for the next providers.
Related Epic: #32634
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the related epic #32634 and the provider-selection spike outcome, then inspect AppConfig and ConfigService to understand the existing configuration flow. Define the provider-specific shape and legacy OpenAI migration before implementing it. Done means provider switching selects the correct settings and returns a valid LangChain4j client, with tests covering both behavior and migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ai, backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100