Skip to content



liquibase.configuration.ConfiguredValueModifier implementations allow configuration values to be translated, regardless of the ConfigurationValueProvider which returns them.


A ConfiguredValueModifier can be created that converts the value LOCAL_DB to a localhost connection string.

With that value modifier in place, anywhere a user can configure their url (CLI arguments, environment variables, file, etc.) they can use LOCAL_DB instead of the full connection string.

Execution Order

For each configuration value, Liquibase will run all ConfiguredValueModifier instances based on the value they return from getOrder().

This allows modifiers to modify the values from each other.

API Highlights


If the value modifier can be dynamically discovered, it must have a no-arg constructor and be registered in META-INF/services/liquibase.configuration.ConfiguredValueModifier.

If it will be created programmatically by an integration, it can accept required fields in the constructor and should NOT be registered.


Returns where the modifier falls in the execution order.


Replaces the configured value if necessary. Generally, implementations will look for patterns in the current value but can also know which values to modify based on key names, data types, or anything else in the passed liquibase.configuration.ConfigurationValue.

If the function should not modify the value, it just exits.

public class MyValueModifier implements ConfiguredValueModifier<String> {

    public final void override(ConfiguredValue<String> object) {
        String currentValue = object.getValue();
        if (currentValue == null || !currentValue.toString().equals("LOCAL_DB")) {
                new ProvidedValue(
                        "Local_DB replacement",

API Details

The complete javadocs for liquibase.configuration.ConfiguredValueModifier is available at