Polish
This commit is contained in:
@@ -380,7 +380,7 @@ environment variables or system properties.
|
||||
[[boot-features-external-config-profile-specific-properties]]
|
||||
=== Profile-specific properties
|
||||
In addition to `application.properties` files, profile-specific properties can also be
|
||||
defined using the naming convention `application-{profile}.properties`. The
|
||||
defined using the naming convention `application-{profile}.properties`. The
|
||||
`Environment` has a set of default profiles (by default `[default]`) which are
|
||||
used if no active profiels are set (i.e. if no profiles are explicitly activated
|
||||
then properties from `application-default.properties` are loaded).
|
||||
@@ -529,29 +529,30 @@ context starts. So in this YAML we set a value for `security.user.password` that
|
||||
|
||||
[source,yaml,indent=0]
|
||||
----
|
||||
server:
|
||||
port: 80000
|
||||
---
|
||||
spring:
|
||||
profiles: default
|
||||
security:
|
||||
user:
|
||||
password: weak
|
||||
server:
|
||||
port: 80000
|
||||
---
|
||||
spring:
|
||||
profiles: default
|
||||
security:
|
||||
user:
|
||||
password: weak
|
||||
----
|
||||
|
||||
whereas in this example, the password is always set because it isn't attached to any profile,
|
||||
and it would have to be explicitly reset in all other profiles as necessary:
|
||||
whereas in this example, the password is always set because it isn't attached to any
|
||||
profile, and it would have to be explicitly reset in all other profiles as necessary:
|
||||
|
||||
[source,yaml,indent=0]
|
||||
----
|
||||
server:
|
||||
port: 80000
|
||||
security:
|
||||
user:
|
||||
password: weak
|
||||
server:
|
||||
port: 80000
|
||||
security:
|
||||
user:
|
||||
password: weak
|
||||
----
|
||||
|
||||
|
||||
|
||||
[[boot-features-external-config-yaml-shortcomings]]
|
||||
==== YAML shortcomings
|
||||
YAML files can't be loaded via the `@PropertySource` annotation. So in the
|
||||
|
||||
Reference in New Issue
Block a user