Detect bad properties in profile specific files
Throw an `InvalidConfigDataPropertyException` if bad properties are detected in profile specific files. The following properties will now trigger an exception if used in a profile specific file: `spring.profiles.include` `spring.profiles.active` `spring.profiles.default` `spring.config.activate.on-profile` `spring.profiles` Prior to this commit, profile based properties in a profile specific file would be silently ignored, making them hard to find. Fixes gh-24733
Showing
Please register or sign in to comment