Skip to content

Commit 8d53caa

Browse files
committed
Merge branch '2.7.x' into 3.0.x
2 parents e5c8723 + 54313d1 commit 8d53caa

File tree

4 files changed

+26
-11
lines changed

4 files changed

+26
-11
lines changed

spring-boot-project/spring-boot-docs/src/docs/asciidoc/web/servlet.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -604,6 +604,7 @@ For example, adding the following bean will automatically apply a `SameSite` of
604604
include::code:MySameSiteConfiguration[]
605605

606606

607+
607608
[[web.servlet.embedded-container.customizing.encoding]]
608609
===== Character Encoding
609610
The character encoding behavior of the embedded servlet container for request and response handling can be configured using the `server.servlet.encoding.*` configuration properties.

spring-boot-project/spring-boot-test-autoconfigure/src/main/java/org/springframework/boot/test/autoconfigure/web/reactive/AutoConfigureWebTestClient.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
/*
2-
* Copyright 2012-2032 the original author or authors.
2+
* Copyright 2012-2023 the original author or authors.
33
*
44
* Licensed under the Apache License, Version 2.0 (the "License");
55
* you may not use this file except in compliance with the License.

spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/packaging-oci-image.adoc

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -397,9 +397,10 @@ The publish option can be specified on the command line as well, as shown in thi
397397
$ gradle bootBuildImage --imageName=docker.example.com/library/my-app:v1 --publishImage
398398
----
399399

400+
401+
400402
[[build-image.examples.caches]]
401403
=== Builder Cache Configuration
402-
403404
The CNB builder caches layers that are used when building and launching an image.
404405
By default, these caches are stored as named volumes in the Docker daemon with names that are derived from the full name of the target image.
405406
If the image name changes frequently, for example when the project version is used as a tag in the image name, then the caches can be invalidated frequently.
@@ -418,12 +419,15 @@ include::../gradle/packaging/boot-build-image-caches.gradle[tags=caches]
418419
include::../gradle/packaging/boot-build-image-caches.gradle.kts[tags=caches]
419420
----
420421

422+
423+
421424
[[build-image.examples.docker]]
422425
=== Docker Configuration
423426

427+
428+
424429
[[build-image.examples.docker.minikube]]
425430
==== Docker Configuration for minikube
426-
427431
The plugin can communicate with the https://minikube.sigs.k8s.io/docs/tasks/docker_daemon/[Docker daemon provided by minikube] instead of the default local connection.
428432

429433
On Linux and macOS, environment variables can be set using the command `eval $(minikube docker-env)` after minikube has been started.
@@ -442,9 +446,10 @@ include::../gradle/packaging/boot-build-image-docker-host.gradle[tags=docker-hos
442446
include::../gradle/packaging/boot-build-image-docker-host.gradle.kts[tags=docker-host]
443447
----
444448

449+
450+
445451
[[build-image.examples.docker.podman]]
446452
==== Docker Configuration for podman
447-
448453
The plugin can communicate with a https://podman.io/[podman container engine].
449454

450455
The plugin can be configured to use podman local connection by providing connection details similar to those shown in the following example:
@@ -463,9 +468,10 @@ include::../gradle/packaging/boot-build-image-docker-host-podman.gradle.kts[tags
463468

464469
TIP: With the `podman` CLI installed, the command `podman info --format='{{.Host.RemoteSocket.Path}}'` can be used to get the value for the `docker.host` configuration property shown in this example.
465470

471+
472+
466473
[[build-image.examples.docker.colima]]
467474
==== Docker Configuration for Colima
468-
469475
The plugin can communicate with the Docker daemon provided by https://github.com/abiosoft/colima[Colima].
470476
The `DOCKER_HOST` environment variable can be set by using the command `export DOCKER_HOST=$(docker context inspect colima -f '{{.Endpoints.docker.Host}}').`
471477

@@ -483,9 +489,10 @@ include::../gradle/packaging/boot-build-image-docker-host-colima.gradle[tags=doc
483489
include::../gradle/packaging/boot-build-image-docker-host-colima.gradle.kts[tags=docker-host]
484490
----
485491

492+
493+
486494
[[build-image.examples.docker.auth]]
487495
==== Docker Configuration for Authentication
488-
489496
If the builder or run image are stored in a private Docker registry that supports user authentication, authentication details can be provided using `docker.builderRegistry` properties as shown in the following example:
490497

491498
[source,groovy,indent=0,subs="verbatim,attributes",role="primary"]

spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/packaging-oci-image.adoc

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -378,9 +378,10 @@ and reference the properties in the XML configuration:
378378
include::../maven/packaging-oci-image/docker-pom-authentication-command-line.xml[tags=docker]
379379
----
380380

381+
382+
381383
[[build-image.examples.caches]]
382384
=== Builder Cache Configuration
383-
384385
The CNB builder caches layers that are used when building and launching an image.
385386
By default, these caches are stored as named volumes in the Docker daemon with names that are derived from the full name of the target image.
386387
If the image name changes frequently, for example when the project version is used as a tag in the image name, then the caches can be invalidated frequently.
@@ -392,12 +393,15 @@ The cache volumes can be configured to use alternative names to give more contro
392393
include::../maven/packaging-oci-image/caches-pom.xml[tags=caches]
393394
----
394395

396+
397+
395398
[[build-image.examples.docker]]
396399
=== Docker Configuration
397400

401+
402+
398403
[[build-image.examples.docker.minikube]]
399404
==== Docker Configuration for minikube
400-
401405
The plugin can communicate with the https://minikube.sigs.k8s.io/docs/tasks/docker_daemon/[Docker daemon provided by minikube] instead of the default local connection.
402406

403407
On Linux and macOS, environment variables can be set using the command `eval $(minikube docker-env)` after minikube has been started.
@@ -409,9 +413,10 @@ The plugin can also be configured to use the minikube daemon by providing connec
409413
include::../maven/packaging-oci-image/docker-minikube-pom.xml[tags=docker-minikube]
410414
----
411415

416+
417+
412418
[[build-image.examples.docker.podman]]
413419
==== Docker Configuration for podman
414-
415420
The plugin can communicate with a https://podman.io/[podman container engine].
416421

417422
The plugin can be configured to use podman local connection by providing connection details similar to those shown in the following example:
@@ -423,9 +428,10 @@ include::../maven/packaging-oci-image/docker-podman-pom.xml[tags=docker-podman]
423428

424429
TIP: With the `colima` CLI installed, the command `podman info --format='{{.Host.RemoteSocket.Path}}'` can be used to get the value for the `docker.host` configuration property shown in this example.
425430

431+
432+
426433
[[build-image.examples.docker.colima]]
427434
==== Docker Configuration for Colima
428-
429435
The plugin can communicate with the Docker daemon provided by https://github.com/abiosoft/colima[Colima].
430436
The `DOCKER_HOST` environment variable can be set by using the command `export DOCKER_HOST=$(docker context inspect colima -f '{{.Endpoints.docker.Host}}').`
431437

@@ -436,9 +442,10 @@ The plugin can also be configured to use Colima daemon by providing connection d
436442
include::../maven/packaging-oci-image/docker-colima-pom.xml[tags=docker-colima]
437443
----
438444

445+
446+
439447
[[build-image.examples.docker.auth]]
440448
==== Docker Configuration for Authentication
441-
442449
If the builder or run image are stored in a private Docker registry that supports user authentication, authentication details can be provided using `docker.builderRegistry` parameters as shown in the following example:
443450

444451
[source,xml,indent=0,subs="verbatim,attributes",tabsize=4]

0 commit comments

Comments
 (0)