Ensure all properties map nicely to yaml
See original GitHub issuelogging.file=logs/app.log
logging.file.max-history=20
logging.file.max-size=50MB
how to config these properties in yml file
#log
logging:
file: // how to config
max-history: 30
max-size: 50MB
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
What is the correct use of the property map read from .yaml ...
What is the correct use of the property map read from .yaml with @Value Spring Annotation ; @Value("#{${app.map}}") private Map<String, String> ...
Read more >Inject a Map from a YAML File with Spring - Baeldung
Learn how to inject a Map from a YAML file in Spring Boot. ... Then we'll demonstrate how to bind YAML properties to...
Read more >24. Externalized Configuration - Spring
You can use properties files, YAML files, environment variables, and command-line arguments to externalize configuration.
Read more >Tips, Tricks, Troubleshooting - yq - GitBook
Yaml files can be surprisingly lenient in what can be parsed as a yaml file. A reasonable way of validation a yaml file...
Read more >10 YAML tips for people who hate YAML | Enable Sysadmin
Computers tend to do well with predictability, so the concept of a linter ... You might be stuck with YAML because that's the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think I finally understand the issue here. A sample would have been very useful. As would have including the full stack trace.
Given the following YAML:
The following exception is raised:
You can work around it by doing this:
I couldn’t find any other properties that can’t be mapped in YAML.
spring.profiles
when combined withspring.profiles.include/active
seems to be the only one and I don’t think we should do anything about that till we decide how we want to handle include profiles in profile-specific YAML documents.I’m in favor of closing this issue now that
logging.file
has been renamed tologging.file.name
.