How to refactor configuration properties?

[tobiasschaefer]

How can configuration properties be refactored while still supporting the old structure?

E.g. I have a supported property "x.y..z" and I want to remove "y" so that it is "x.z" but I still want to support x.y.z and preferably log a warning if it is used?

This is the existing structure:

@ConfigurationProperties( "x")
public interface Configuration {

    @NotNull
    Y getY();

    @ConfigurationProperties("y")
    interface Y {

        @Bindable(defaultValue = "false")
        boolean isZ();
    }
}

This would be the new structure but it misses "y" completely:

@ConfigurationProperties( "x")
public interface Configuration {

    @Bindable(defaultValue = "false")
     boolean isZ();
}

So how must I implement to support both?

Do you have any hints?

[graemerocher]

Don't think this is currently supported with interfaces, but I recommend reporting an issue with a feature request and we can see what we can do

[tobiasschaefer]

Actually, my use case is very specific. I guess it would need a more generic concept how to handle deprecated properties.

@graemerocher: Shall I file an issue for that instead? Maybe simply log a warning to every configuration (node and leaf) that as been marked as @Deprecated.

Note: I'm now checking environment.getPropertyEntries("x.y").isEmpty() and throwing an exception on startup if there are any old configurations. That is sufficient for my use case.

[graemerocher]

Yes file an issue

[tobiasschaefer]

Files as #4967