What causes "Set command must be in the form key=value" in quarkusio/quarkus?

Enter the command as key=value, e.g. set quarkus.datasource.jdbc.url=jdbc:postgresql://localhost/test

quarkusio/quarkus · error · CommandValidatorException

Set command must be in the form key=value

Error message

Set command must be in the form key=value

What it means

ConsoleProcessor's command validation for the dev-mode console 'set' command requires a '=' separator so the value can be split into key and value. CommandValidatorException is thrown when no '=' appears anywhere except possibly as the last character. This is a live dev-console input validation, not a build failure.

Source

Thrown at extensions/vertx-http/deployment/src/main/java/io/quarkus/vertx/http/deployment/devmode/ConsoleProcessor.java:230

                }
            }
            completerInvocation.setAppendSpace(false);
            completerInvocation.addAllCompleterValues(possible);

        }
    }

    public static class SetValidator implements CommandValidator<SetConfigCommand, CommandInvocation> {

        @Override
        public void validate(SetConfigCommand command) throws CommandValidatorException {
            //-1 because the last char can't be equals
            for (int i = 0; i < command.command.length() - 1; ++i) {
                if (command.command.charAt(i) == '=') {
                    return;
                }
            }
            throw new CommandValidatorException("Set command must be in the form key=value");
        }
    }
}

View on GitHub (pinned to e1c734241f)

Solutions

Enter the command as key=value, e.g. set quarkus.datasource.jdbc.url=jdbc:postgresql://localhost/test
Ensure the '=' is not the final character — a value after '=' is expected
Escape or quote values containing spaces per the console's syntax if needed

Example fix

// before (dev console input)
set quarkus.log.level
// after
set quarkus.log.level=DEBUG

Defensive patterns

Strategy: validation

Validate before calling

boolean validSetCommand(String cmd) {
    int eq = cmd.indexOf('=');
    return eq > 0 && eq < cmd.length() - 1; // key before '=', value after
}

Try / catch

try {
    console.execute(command);
} catch (CommandValidatorException e) {
    // prompt user: command must be key=value
}

Prevention

Always include a non-empty value: key=value, with '=' not the last character
Double-check pasted dev-console commands for lost '=value' suffixes
Remember the check scans the whole string for '=' anywhere except the final position — 'key=' still fails in spirit since the value is empty

When it happens

Trigger: Typing a 'set' command in the Quarkus dev console (dev mode terminal) whose command string contains no '=' character within its length minus the final char — e.g. 'set mykey' or 'set mykey='.

Common situations: Forgetting the value when setting a system property via the dev console; pasting commands that lost the '=value' portion; interactive typos.

Related errors

AI-assisted analysis of quarkusio/quarkus@e1c734241f (2026-09-05). Data as JSON: /api/errors/f989329e8d8c5f20. Report an issue: GitHub.