Spring Boot required import: fail when a relative file is missing

Last updated: 30 Sept 20264 min read

tutorial

A required relative Spring Boot configuration import prevents the checked child process from starting when the file is absent.

Download Spring source kit

Failure at the same boundary

The test creates config/application.properties with spring.config.import=relay/missing.properties and does not create that imported file. A child JVM receives the config directory as an additional location. It exits nonzero and never prints a successful bound value. The earlier context test checked a missing file URI inside one JVM; this check adds a launched-process boundary and a relative path.

Use a required import when its absence must stop work. A different policy may allow a developer-only override to be optional. The optional test proves a fallback for one missing local file; it should not be copied to a required credential.

Other failures still need checks

The child does not test unreadable permissions, a partially written file, a wrong key, a malformed secret or rotation during a running process. A successful import also says nothing about the validity of the loaded values until binding and validation run. The invalid-value check covers one such boundary.

Checked source

spring.config.import=relay/missing.properties
# No config/relay/missing.properties exists; child exits nonzero.

Verification boundary

RelaySettingsProcessTest.missingRequiredRelativeImportStopsTheChildProcess. The source kit contains the full test and entry point.

Common Mistakes

Do not turn a required deployment file into an optional import just to clear a startup error.
Do not interpret a nonzero exit as proof of a specific exception text across Boot versions.
Do not put a secret value in a startup diagnostic.

Checked config-data continuation

Continue with Spring Boot nested import failure: a missing second hop must stop startup.

spring

configuration

testing