You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> This article previously recommended using the [Paketo Java Azure Composite Buildpack](https://github.com/paketo-buildpacks/java-azure), which is discontinued. We've updated the example to use the necessary individual components of the composite buildpack. For a list of all individual components included in the composite buildpack, please refer to [buildpack.toml](https://github.com/paketo-buildpacks/java-azure/blob/main/buildpack.toml). For more information about the discontinuation of the composite buildpack, see [Paketo Buildpacks Sunsets Java Azure Composite Buildpack](https://blog.paketo.io/posts/paketo-java-azure-sunsets/).
21
-
22
19
This article describes how to build a container image by using Paketo Buildpacks.
23
20
24
21
Azure Spring Apps service supports building an image from source code without using Dockerfiles. It isn't limited to Java applications but extends to other programming languages and even static web content. In the Standard plan, the service uses open-source [Paketo Buildpacks](https://paketo.io/), while in Enterprise plan, it uses VMware Tanzu Buildpacks. If Tanzu Buildpacks are unavailable or there's no online service for using Paketo, you can switch to local Paketo Buildpacks to build images. Then deploy them to Azure Container Registry or other Docker registries.
25
22
26
23
This article shows you how to create a builder with a TOML file, and then build your source code or artifact file with the builder. For more information, see [builder.toml](https://buildpacks.io/docs/reference/config/builder-config/). To understand the build image, run image, and stack, see [What are base images](https://buildpacks.io/docs/for-app-developers/concepts/base-images/).
27
24
25
+
> [!NOTE]
26
+
> This article previously recommended using the [Paketo Java Azure Composite Buildpack](https://github.com/paketo-buildpacks/java-azure), which is discontinued. We've updated the example to use the necessary individual components of the composite buildpack. For a list of all individual components included in the composite buildpack, see [buildpack.toml](https://github.com/paketo-buildpacks/java-azure/blob/main/buildpack.toml). For more information about the discontinuation of the composite buildpack, see [Paketo Buildpacks Sunsets Java Azure Composite Buildpack](https://blog.paketo.io/posts/paketo-java-azure-sunsets/).
The Azure Spring Apps Standard plan comes with a built-in builder, which you can't customize. To replace this builder, you need to create a TOML file for your own builder. Below is an example TOML file that can be customized to build a Java Spring Boot app with Application Insights. Please adjust the TOML file based on your app's requirements.
35
+
The Azure Spring Apps Standard plan comes with a built-in builder, which you can't customize. To replace this builder, you need to create a TOML file for your own builder. The following TOML file is an example that you can customize to build a Java Spring Boot app with Application Insights. Adjust the TOML file based on your app's requirements.
36
36
37
37
```toml
38
38
# filename: standard-builder.toml
@@ -205,7 +205,7 @@ The following table shows the Paketo Buildpack equivalents to the buildpacks use
To replace the builder in the Enterprise plan, you need to create a TOML file for your own builder. Below is an example TOML file that can be customized. With this TOML file, you can create a similar builder on your local machine. Please adjust the TOML file based on your app's requirements.
208
+
To replace the builder in the Enterprise plan, you need to create a TOML file for your own builder. The following TOML file is an example that you can be customize. With this TOML file, you can create a similar builder on your local machine. Adjust the TOML file based on your app's requirements.
0 commit comments