spring.ai.openai.moderation.options.* properties ignored due to immutable initialization in OpenAiModerationProperties

[jacquicollier2-eng]

Description

When configuring the OpenAI Moderation model in application.yml, the property:

spring:
  ai:
    openai:
      moderation:
        options:
          model: omni-moderation

is silently ignored — the model always defaults to text-moderation-latest.

Root cause

In OpenAiModerationProperties, the options field is initialized via a builder call that immediately constructs an immutable OpenAiModerationOptions instance:

@NestedConfigurationProperty
private final OpenAiModerationOptions options = OpenAiModerationOptions.builder().build();

Because:

the field is final,

the instance is pre-built, and

there is no setter,

Spring Boot’s @ConfigurationProperties binder cannot modify or replace this object.
Thus, the YAML values under spring.ai.openai.moderation.options.* are never applied.

Expected behavior

The YAML configuration should override the model, e.g.:

spring:
  ai:
    openai:
      moderation:
        options:
          model: omni-moderation

should cause OpenAiModerationOptions.getModel() to return "omni-moderation".

Proposed fix

In OpenAiModerationProperties, replace the current initialization with a mutable, bindable instance:

@NestedConfigurationProperty
private final OpenAiModerationOptions options = new OpenAiModerationOptions();

or, ideally, make it non-final and add a setter:

@NestedConfigurationProperty
private OpenAiModerationOptions options = new OpenAiModerationOptions();

public void setOptions(OpenAiModerationOptions options) {
this.options = options;
}

This allows Spring Boot’s configuration binder to correctly populate nested properties.

[quaff]

In OpenAiModerationProperties, replace the current initialization with a mutable, bindable instance:

@NestedConfigurationProperty private final OpenAiModerationOptions options = new OpenAiModerationOptions();

or, ideally, make it non-final and add a setter:

@NestedConfigurationProperty private OpenAiModerationOptions options = new OpenAiModerationOptions();

public void setOptions(OpenAiModerationOptions options) { this.options = options; }

This allows Spring Boot’s configuration binder to correctly populate nested properties.

It's not caused by properties binding, unit test added by #4713 doesn't fail.
Please double check.

[ilayaperumalg]

@jacquicollier2-eng Thanks for reporting. @quaff Thanks for the quick follow up adding tests to verify the behaviour!

@jacquicollier2-eng Please verify and close the issue.

[jacquicollier2-eng]

Thanks for verifying that, but there is definitely still something which prevents the property from being picked up.

Problem is that it seems to not happen consistently. I added the property to the yaml file a couple of days ago. The first deploy worked fine and used the new model. Subsequent deploys went back to using the default model.

I'm using Spring AI 1.1.0-M3.

I will try to put together an example project, but unfortunately it doesn't seem happen all the time.