Check the file lookup and validation contracts before changing a deployment config path.
Review before answering
- Spring Boot nested config imports: each file becomes the next base directory
- Spring Boot nested import failure: a missing second hop must stop startup
- Spring Boot configtree: bind one file per property in a child JVM
- Spring Boot configtree versus environment: assert the effective value
- Spring Boot required configtree: reject an absent directory
- Spring Boot configtree validation: reject a present but unsafe value
- Spring Boot extensionless config file: give the loader a properties hint
Common Mistakes
- Do not resolve every import from the first file.
- Do not confuse a loaded file with a valid value.
- Do not call a synthetic tree a platform secret mount.