- Notifications
You must be signed in to change notification settings - Fork 41.6k
Spring Boot 3.4 Configuration Changelog
Configuration property changes between 3.3.6
and 3.4.0
Key | Replacement | Reason |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
| ||
| Deprecated in Flyway 10.18 | |
|
| |
|
| |
|
| |
|
| |
|
|
Key | Default value | Description |
---|---|---|
|
| Whether to include the application group in the logs. |
| Structured ECS service environment. | |
| Structured ECS service name (defaults to 'spring.application.name'). | |
| Structured ECS service node name. | |
| Structured ECS service version (defaults to 'spring.application.version'). | |
| Structured logging format for output to the console. | |
| Structured logging format for output to a file. | |
| Structured GELF host (defaults to 'spring.application.name'). | |
| Structured GELF service version (defaults to 'spring.application.version'). | |
| Additional members that should be added to structured logging JSON | |
| The fully qualified class name of a StructuredLoggingJsonMembersCustomizer | |
| Member paths that should be excluded from structured logging JSON | |
| Member paths that should be included in structured logging JSON | |
| Mapping between member paths and an alternative name that should be used in structured logging JSON | |
|
| Whether to enable _source in the default index template when auto-creating the index. |
|
| Permitted level of access for the auditevents endpoint. |
|
| Permitted level of access for the beans endpoint. |
|
| Permitted level of access for the caches endpoint. |
|
| Permitted level of access for the conditions endpoint. |
|
| Permitted level of access for the configprops endpoint. |
|
| Permitted level of access for the env endpoint. |
|
| Permitted level of access for the flyway endpoint. |
|
| Permitted level of access for the health endpoint. |
|
| Permitted level of access for the heapdump endpoint. |
|
| Permitted level of access for the httpexchanges endpoint. |
|
| Permitted level of access for the info endpoint. |
|
| Permitted level of access for the integrationgraph endpoint. |
|
| Permitted level of access for the liquibase endpoint. |
|
| Permitted level of access for the logfile endpoint. |
|
| Permitted level of access for the loggers endpoint. |
|
| Permitted level of access for the mappings endpoint. |
|
| Permitted level of access for the metrics endpoint. |
|
| Permitted level of access for the prometheus endpoint. |
|
| Permitted level of access for the quartz endpoint. |
|
| Permitted level of access for the sbom endpoint. |
|
| Permitted level of access for the scheduledtasks endpoint. |
|
| Permitted level of access for the sessions endpoint. |
|
| Permitted level of access for the shutdown endpoint. |
|
| Permitted level of access for the startup endpoint. |
|
| Permitted level of access for the threaddump endpoint. |
| Default access level for all endpoints. | |
|
| The maximum level of endpoint access that is permitted. |
|
| If an SSL Certificate will be invalid within the time span defined by this threshold, it should trigger a warning. |
|
| Whether to enable SSL certificate health check. |
|
| Whether to enable SSL certificate info. |
|
| Whether auto-configuration of logging is enabled to export logs. |
|
| Method used to compress the payload. |
|
| Connect timeout for the OTel collector connection. |
| URL to the OTel collector’s HTTP API. | |
| Whether auto-configuration of logging is enabled to export OTLP logs. | |
| Custom HTTP headers you want to pass to the collector, for example auth headers. | |
|
| Call timeout for the OTel Collector to process an exported batch of data. |
|
| Transport used to send the spans. |
|
| Histogram type to be preferred when histogram publishing is enabled. |
|
| Maximum number of buckets to be used for exponential histograms, if configured. |
|
| Max scale to use for exponential histograms, if configured. |
|
| Connect timeout for the OTel collector connection. |
| Whether auto-configuration of tracing is enabled to export OTLP traces. | |
|
| Transport used to send the spans. |
| Whether auto-configuration of tracing is enabled to export Wavefront traces. | |
| Whether auto-configuration of tracing is enabled to export Zipkin traces. | |
|
| Maximum number of form keys. |
| Whether the generated cookie carries the Partitioned attribute. | |
| Whether the generated cookie carries the Partitioned attribute. | |
|
| Whether to enable embedded mode if the ActiveMQ Broker is available. |
| Application group. | |
| Application version (defaults to 'Implementation-Version' from the manifest). | |
| Java KeyStore location for certificate-based cluster authentication. | |
| Java KeyStore password for certificate-based cluster authentication. | |
| Private key password for certificate-based cluster authentication. | |
| PEM-formatted certificates for certificate-based cluster authentication. | |
| PEM-formatted private key for certificate-based cluster authentication. | |
| Private key password for certificate-based cluster authentication. | |
|
| Configures how to render Spring Data Pageable instances. |
| ||
| ||
| ||
| ||
| ||
|
| Whether to enable community database support. |
| Time required for concurrent handling to complete. | |
| Sets how strictly the RFC 8259 specification will be enforced when reading and writing JSON. | |
| Default connect timeout for a client HTTP request. | |
| Default factory used for a client HTTP request. | |
| Default read timeout for a client HTTP request. | |
|
| Handling for HTTP redirects. |
| SSL bundle to use. | |
| Specify the maximum number of messages to process in one task. | |
|
| Canonical backoff period. |
|
| Maximum wait between retries. |
|
| Multiplier to use for generating the next backoff delay. |
|
| Whether to have the backoff delays. |
| SSL bundle name. | |
|
| Whether to enable SSL support. |
| List of locale-independent property file resources containing common messages. | |
| Number of threads to be used for handling connections to brokers. | |
| Number of threads to be used for message listeners. | |
|
| Whether to enable default tenant and namespace support for topics. |
|
| Default namespace to use when producing or consuming messages against a non-fully-qualified topic URL. |
|
| Default tenant to use when producing or consuming messages against a non-fully-qualified topic URL. |
| Number of threads used by listener container. |
Key | Replacement | Reason |
---|---|---|
| ||
| The new InfluxDb Java client provides Spring Boot integration. | |
| The new InfluxDb Java client provides Spring Boot integration. | |
| The new InfluxDb Java client provides Spring Boot integration. | |
| DispatcherServlet property is deprecated for removal and should no longer need to be configured. |