10 Hidden Spring Boot Configuration Tricks to Simplify Your YAML Files

YAML Anchors – Keep datasource configuration DRY

Define a reusable datasource template with a YAML anchor ( &) and reference it with an alias ( *). The merge key ( <<) copies the anchored properties into each datasource definition, so a single change updates all datasources.

# Define a common datasource template
common-datasource: &common-ds
  driver-class-name: com.mysql.cj.jdbc.Driver
  username: ${DB_USER:root}
  password: ${DB_PASSWORD:root}
  hikari:
    minimum-idle: 5
    maximum-pool-size: 20
    connection-timeout: 30000

spring:
  datasource:
    primary:
      <<: *common-ds
      url: jdbc:mysql://master.pigx.vip:3306/pig
    replica:
      <<: *common-ds
      url: jdbc:mysql://slave.pigx.vip:3306/pig

Externalizing Sensitive Files

Load a local .env file optionally using spring.config.import. The file should be added to .gitignore to avoid committing secrets.

# application.yml
spring:
  config:
    import: optional:file:.env[.properties]

app:
  api-key: ${MY_API_KEY}
  secret: ${MY_SECRET}

# .env (add to .gitignore)
MY_API_KEY=sk-xxxxxxxxxxxx
MY_SECRET=your-secret-here

Environment Variable Injection with Safe Defaults

Use the ${VAR:default} syntax to provide fallback values, allowing the application to start locally without any environment variables while production can override them.

spring:
  datasource:
    url: ${DB_URL:jdbc:mysql://localhost:3306/pig}
    username: ${DB_USER:root}
    password: ${DB_PASSWORD:root}

server:
  port: ${SERVER_PORT:8080}

Profile Group Activation

Define profile groups so a single logical profile activates multiple concrete profiles.

# application.yml
spring:
  profiles:
    group:
      production:
        - proddb
        - security
        - metrics
      development:
        - devdb
        - swagger

Run the application with a short command:

java -jar pig-gateway.jar --spring.profiles.active=production

Property Cross‑Reference

Store values such as service name and version once and reference them elsewhere with ${property.name}.

pig:
  service:
    name: pig-gateway
    version: 4.0.0
  logging:
    path: /var/log/${pig.service.name}/
  metrics:
    prefix: ${pig.service.name}_${pig.service.version}

spring:
  application:
    name: ${pig.service.name}

Single‑File Multi‑Environment Management

Use YAML multi‑document syntax ( ---) together with spring.config.activate.on-profile to keep all environment configurations in one file.

# application.yml (common)
server:
  port: 8080
spring:
  application:
    name: pig-gateway
---
# Development profile
spring:
  config:
    activate:
      on-profile: dev
server:
  port: 9999
---
# Production profile
spring:
  config:
    activate:
      on-profile: prod
server:
  port: 80

Conditional Import of External Config

Import optional external configuration files that may be provided by customers. If the file does not exist, the import is ignored.

# application.yml
spring:
  config:
    import:
      - optional:file:/etc/pig/custom-config.yml
      - optional:classpath:override.yml

Structured Configuration with Type Safety

Bind hierarchical configuration to a Java record using @ConfigurationProperties. This provides immutability, thread‑safety, and automatic type conversion (e.g., 2s → Duration).

# application.yml
pig:
  notification:
    retry:
      count: 3
      delay: 2s
      enabled: true
      channels:
        - sms
        - email

package com.pig4cloud.pigx.common.config;

import org.springframework.boot.context.properties.ConfigurationProperties;
import java.time.Duration;
import java.util.List;

@ConfigurationProperties(prefix = "pig.notification.retry")
public record PigRetryProperties(
    int count,
    Duration delay,
    boolean enabled,
    List<String> channels
) {}

Random Value Generation

Generate unique identifiers or random ports for testing using ${random.*} expressions.

pig:
  instance-id: ${random.uuid}
  random-port: ${random.int[10000,65535]}
  session-seed: ${random.long}

server:
  port: ${random.int[8000,9000]}

${random.uuid}

– UUID ${random.int} – Random integer ${random.int(max)} – 0 to max ${random.int[min,max]} – min to max ${random.long} – Random long integer

Each read generates a new value; bind the random value to a bean if a stable value is required across the application.

Cloud‑Platform Auto‑Detection

Activate configuration conditionally based on the detected cloud platform using on-cloud-platform. This allows different settings for local development and Kubernetes deployments without extra startup parameters.

# Default configuration
spring:
  lifecycle:
    timeout-per-shutdown-phase: 10s
---
# Only effective on Kubernetes
spring:
  config:
    activate:
      on-cloud-platform: kubernetes
  lifecycle:
    timeout-per-shutdown-phase: 30s
logging:
  level:
    root: INFO

Conclusion

These ten techniques address common configuration pain points: duplicated files, repeated settings, insecure secret handling, and cumbersome multi‑environment switches. Since Spring Boot 2.4, the ConfigData API provides native support for anchors, profile groups, conditional imports, type‑safe binding, random values, and cloud‑platform detection, enabling concise and secure configuration management without external config servers.