New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove spring.config.use-legacy-processing
in tests
#4900
Conversation
Motivation: When we upgrade to Spring Boot 2.4, we used `spring.config.use-legacy-processing` property because main application.yml overrides the yaml files in test. However, it was a bug and fixed. spring-projects/spring-boot#24719 Therefore, we don't have to use `spring.config.use-legacy-processing` anymore. Modifications: - Remove `spring.config.use-legacy-processing` property Result: - Close line#4899
@@ -6,4 +6,4 @@ spring.config.activate.on-profile: local | |||
armeria: | |||
ports: | |||
- port: 8080 | |||
protocol: HTTP | |||
protocols: HTTP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This field is a list and we can just specify the element without enclosing brackets. e.g. [HTTP]
It's because Spring has relaxed rule for the list value.
However, this doesn't apply to Dropwizard so we cannot use the same rule.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for cleaning this up, @minwoox! 🙇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @minwoox ! 👍 🙇 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for cleaning up!
Motivation:
When we upgrade to Spring Boot 2.4, we used
spring.config.use-legacy-processing
property because main application.yml overrides the yaml files in the test. However, it was a bug and was fixed.spring-projects/spring-boot#24719 Therefore, we don't have to use
spring.config.use-legacy-processing
anymore.Modifications:
spring.config.use-legacy-processing
propertyResult:
spring.config.use-legacy-processing
in our test application file #4899