bootstrap-xxx.yml is not loaded with spring.profiles.include=xxx
See original GitHub issueAs described at here, bootstrap-xxx.yml is loaded with spring.profiles.active=xxx only.
But it does NOT loaded with spring.profiles.include=xxx ( spring.profiles.include comes from Spring Boot).
Sometimes I prefer to use spring.profiles.include to map an other profile.
It would become more useful if spring.profiles.include were supported.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Set profile on bootstrap.yml in spring cloud to target different ...
I find the solution. Basically, we use spring profile to enrich the bootstrap file. For example spring: application: name: myservice cloud: ...
Read more >Spring Cloud Config
If the YAML files have documents inside them that point to Spring profiles, those are applied with higher precedence (in order of the...
Read more >Spring Configuration Bootstrap vs Application Properties
properties or an application.yaml file. And, of course, the configuration properties of the bootstrap context load before the configuration ...
Read more >Spring Cloud - Application Context Services - bush
yml]" (and friends if Spring profiles are active). If you have a bootstrap.yml (or properties) then those properties are used to configure the...
Read more >It's time to get ready for Spring Boot 3.0
properties or application.yaml , but as of 2.4 spring.profiles.active cannot be used in a specific environment, i.e. application-<profile>.
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
@indraneelb1903 generally speaking, if an issue is open, it has not been implemented.
originally is following:
not: