spring-projects / spring-projects/spring-ai

Support configuring BedrockCacheOptions via application.properties

Open
#4,872 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
1d 7h
Merged PRs (30d)
6

Description

Request

Please consider adding support for configuring BedrockCacheOptions via application configuration properties.

Description

At present, cache options for Bedrock—specifically BedrockCacheOptions and its underlying properties such as strategy—cannot be set via application.properties or application.yaml. In contrast, other options (like those in BedrockChatOptions, including maxTokens, model, etc.) can be configured using the spring.ai.bedrock.converse.chat.options.* properties.

It would be very helpful for Spring Boot users if BedrockCacheOptions could be made configurable via application properties in the same way.

Use Case Example

spring.ai.bedrock.converse.chat.options.cache-options=SYSTEM_AND_TOOLS

or similar, depending on property structure.

Benefit

Improves consistency with the rest of the options.
Enables externalized configuration for different environments.
Empowers users to avoid custom code just to tweak cache strategy.

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 tracing how existing BedrockChatOptions are bound from spring.ai.bedrock.converse.chat.options.* and locate the BedrockCacheOptions entry point. Add equivalent application.properties/application.yaml support for the cache strategy, then verify that the configured value is applied when Bedrock caching is used.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java, spring-boot
Domain
backend, cloud
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.