Merge pull request #1852 from chathuraHarshanga/PE

changing build packs with build presets

Author: JanakaSandaruwan

en/.spelling

@@ -10,8 +10,8 @@ DockerHub
 Quickstart
 Entra
 AzureAD
-buildpack
-buildpacks
+build preset
+build presets
 Temurin
 RabbitMQ
 SalesOrderQueue

en/developer-docs/docs/authentication-and-authorization/secure-web-applications-with-managed-authentication.md

@@ -7,7 +7,7 @@ As a developer, you can easily set up Choreo's managed authentication to seamles
 Choreo's managed authentication follows the backend for frontend (BFF) architecture, which is a secure pattern recommended for browser-based applications that utilize OIDC/OAuth2.0 for authentication and authorization. This architecture ensures that OAuth tokens remain secure from browser-side code, making them immune to potential attacks like cross-site scripting (XSS).
 
 !!! note
-     Choreo's managed authentication is currently available only for web applications created with **React**, **Angular**, or **Vue.js** buildpacks.
+     Choreo's managed authentication is currently available only for web applications created with **React**, **Angular**, or **Vue.js** build presets.
 
 !!! warning
      Managed authentication uses the 'SAMESITE' cookie attribute to prevent CSRF attacks. Therefore, it is recommended to use managed authentication with modern browsers that support the 'SAMESITE' attribute.
@@ -172,7 +172,7 @@ To ensure that your web application functions seamlessly with managed authentica
 You can enable managed authentication for your web application component at the time you deploy the component.
 
 !!! tip
-     Managed authentication is enabled by default when you create a web application using **React**, **Angular**, or **Vue.js** buildpacks.
+     Managed authentication is enabled by default when you create a web application using **React**, **Angular**, or **Vue.js** build presets.
 
 1. Sign in to the [Choreo Console](https://console.choreo.dev/). This opens the project home page.
 2. In the **Component Listing** pane, click on the web application for which you want to enable managed authentication.

en/developer-docs/docs/choreo-cli/get-started-with-the-choreo-cli.md

@@ -88,7 +88,7 @@ This triggers a wizard prompting you to provide details for your Git repository
     | Port                        | `8080`                                 |
 
     !!! note
-        The prompts may vary based on the type of component and the chosen build pack. 
+        The prompts may vary based on the type of component and the chosen build preset. 
 
 
 ## Step 4: View component details

en/developer-docs/docs/choreo-concepts/ci-cd.md

@@ -24,7 +24,7 @@ Choreo auto-generates build pipelines that may slightly differ depending on the
 - Pushes the container image to a container registry. In the cloud data plane, Choreo pushes the image to a Choreo-managed registry. If it is a private data plane organization, Choreo pushes the image to a registry that you own.
 - Updates service endpoints and API specifications from the provided repository if applicable.
 
-In addition to these steps, some buildpacks support integrating unit tests into the build pipeline. For more details, see [Integrate Unit Tests into the Build Pipeline](../develop-components/integrate-unit-tests-into-the-build-pipeline.md).
+In addition to these steps, some build presets support integrating unit tests into the build pipeline. For more details, see [Integrate Unit Tests into the Build Pipeline](../develop-components/integrate-unit-tests-into-the-build-pipeline.md).
 
 ### Repeatable builds
 

en/developer-docs/docs/choreo-samples/samples-overview.md

@@ -29,7 +29,7 @@ To view available samples, follow these steps:
 
 When you view all samples, you can filter and search for samples by the following criteria:
 
-- **Buildpack**: Filters by the technology used. For example, Ballerina, NodeJS, Docker, etc.
+- **Build preset**: Filters by the technology used. For example, Ballerina, NodeJS, Docker, etc.
 - **Component Type**: Filters by the component type. For example, service, web application, scheduled tasks, manual tasks, etc.
 - **Tags**: Use tags like REST, HTTP, or GraphQL to find samples with specific functionalities or integrations.
 

en/developer-docs/docs/develop-components/configure-endpoints-body.md

@@ -13,10 +13,10 @@ Choreo defines endpoints by combining port binding, protocol, endpoint name, net
 | Context (HTTP and GraphQL only) | A context path that you add to the endpoint's URL for routing purposes. |
 
 ## Configure endpoints
-The method of defining endpoints depends on the buildpack.
+The method of defining endpoints depends on the build preset.
 
-* For `Ballerina` and `WSO2 MI` buildpacks, Choreo automatically detects the endpoint details for REST APIs.
-* For all other buildpacks (Java, Python, NodeJS, Ruby, PHP, Go, Dockerfile, etc.), you can configure endpoints in one of the following ways:
+* For `Ballerina` and `WSO2 MI` build presets, Choreo automatically detects the endpoint details for REST APIs.
+* For all other build presets (Java, Python, NodeJS, Ruby, PHP, Go, Dockerfile, etc.), you can configure endpoints in one of the following ways:
 
     * **Using the Choreo Console**: If a `component.yaml` file is not present, you can define a basic endpoint configuration during component creation.
     * **Using the component.yaml file**: You can manually configure endpoint details by defining them in a `component.yaml` file, placing it inside the `.choreo` directory at the build context path, and committing it to the source repository.

en/developer-docs/docs/develop-components/deploy-a-containerized-application.md

@@ -42,7 +42,7 @@ Alternatively, you can connect a public repository without requiring authorizati
      Authorizing the repository with the [Choreo Apps](https://github.com/marketplace/choreo-apps) GitHub application becomes essential if you want to enable [**Auto Deploy**](https://wso2.com/choreo/docs/choreo-concepts/ci-cd/#deploy) for the component. If you own the repository, you can subsequently authorize it with the [Choreo Apps](https://github.com/marketplace/choreo-apps) GitHub application to enable **Auto Deploy**.
 
 After granting access to the required repositories, you can choose a repository and an associated branch to connect to the Choreo component.
-For the containerized application deployments, you should select the [**Component Directory**](https://docs.docker.com/build/building/context/#path-context), **Dockerfile** as the **Buildpack** and provide **Dockerfile Path** for the Docker build.
+For the containerized application deployments, you should select the [**Component Directory**](https://docs.docker.com/build/building/context/#path-context), **Dockerfile** as the **Build preset** and provide **Dockerfile Path** for the Docker build.
 
 ![Connected Dockerfile Repository](../assets/img/develop-components/deploy/create-component-connected-repo.png){.cInlineImage-full}
 
@@ -53,7 +53,7 @@ The following table describes the individual fields in the **Create Component**
 | **GitHub Account**      | Your GitHub account or organization. If you want to add another GitHub account, you can expand the list and click **+ Add**.                                                            |
 | **GitHub Repository**   | Depending on the repository access you provided, the list will show available repositories to be connected.                                                                                  |
 | **Branch**              | The branch of the repository.                                                                                                                                                         |
-| **Buildpack**        | Determines the implementation of the component: Any language or other language as a Docker container.                                                                                |
+| **Build preset**        | Determines the implementation of the component: Any language or other language as a Docker container.                                                                                |
 | **Dockerfile Path**     | The path to your Dockerfile. This path is defined relative to the repository root.<br/>For example, if the Dockerfile is at the repository root, the value for this field is `/Dockerfile`. |
 | **Component Directory** | The component directory path. To include the repository root, leave the default `/` value.                                                                                          |
 | **Port***               | The port at which your service is running.                                                                                                                                           |

en/developer-docs/docs/develop-components/deploy-an-application-with-buildpacks.md

@@ -1,8 +1,8 @@
-# Deploy an Application with Buildpacks
+# Deploy an Application with Build Presets
 
 Using Choreo, you can easily deploy applications written in different language frameworks (such as Java, Go, NodeJS, Python, Ruby, PHP, etc.) on shared or private data planes.
 
-Choreo supports deploying applications with buildpacks for the following component types:
+Choreo supports deploying applications with build presets for the following component types:
 
 - Service
 - Web Application
@@ -12,10 +12,10 @@ Choreo supports deploying applications with buildpacks for the following compone
 - Event Handler
 - Test Runner
 
-## Buildpacks
-Buildpacks are a fundamental building block in modern application development. They convert your source code into a secure, efficient, production-ready container image without a Dockerfile. With Choreo, developers can take advantage of this powerful tool to effortlessly deploy their applications without the hassle of manual configuration.
+## Build Presets
+Build presets are a fundamental building block in modern application development. They convert your source code into a secure, efficient, production-ready container image without a Dockerfile. With Choreo, developers can take advantage of this powerful tool to effortlessly deploy their applications without the hassle of manual configuration.
 
-Choreo uses [Google Buildpacks](https://cloud.google.com/docs/buildpacks/overview) as default buildpacks for Java, Go, NodeJS, Python, PHP, and Ruby. Choreo uses its own buildpacks for Ballerina and WSO2 MI.
+Choreo uses [Google Buildpacks](https://cloud.google.com/docs/buildpacks/overview) as default build presets for Java, Go, NodeJS, Python, PHP, and Ruby. Choreo uses its own build presets for Ballerina and WSO2 MI.
 
 ## Develop a component
 
@@ -159,25 +159,25 @@ Follow the guidelines below based on your language:
         - 8, 11, 17, 18 (OpenJDK Runtime Environment Temurin)
 
     !!! info
-         You can use this buildpack only with web applications. For other component types, use the **Java** buildpack. Additionally, if the generated artifact is a `WAR` file, you must include the run command in the **Build Configurations** editor on the component's **Build** page. <br> e.g.,
+         You can use this build preset only with web applications. For other component types, use the **Java** build preset. Additionally, if the generated artifact is a `WAR` file, you must include the run command in the **Build Configurations** editor on the component's **Build** page. <br> e.g.,
             `java -jar target/sample.war` <br>
 
 ### Configure build-time environment variables
 
 You can configure the environment variables necessary to build the component using the **Build Configurations Editor** on the component **Build** page. 
 
 !!! info
-    The capability to configure build-time environment variables is not available for components created using **Ballerina** or **WSO2 MI** buildpacks.
+    The capability to configure build-time environment variables is not available for components created using **Ballerina** or **WSO2 MI** build presets.
 
-During the build process, the build-time environment variables and their values are passed to the buildpack. Therefore, you can configure both buildpack-specific environment variables and those required for the component build.
+During the build process, the build-time environment variables and their values are passed to the build preset. Therefore, you can configure both build preset-specific environment variables and those required for the component build.
 
-For example, if you want to override the Maven command of the **Java** buildpack, you can use `GOOGLE_MAVEN_BUILD_ARGS` as the environment key and `clean install` as the value. 
+For example, if you want to override the Maven command of the **Java** build presets, you can use `GOOGLE_MAVEN_BUILD_ARGS` as the environment key and `clean install` as the value. 
 
 For more examples, see [Google Cloud's buildpacks documentation](https://cloud.google.com/docs/buildpacks/service-specific-configs).
 
 ### Customize the Default Run Command
 
-You can configure the run command required to start the component via the **Build Configurations** editor on the component's **Build** page. This overrides the default run command provided by the buildpack. After configuring the run command, you must rebuild the component for the changes to take effect.<br>
+You can configure the run command required to start the component via the **Build Configurations** editor on the component's **Build** page. This overrides the default run command provided by the build preset. After configuring the run command, you must rebuild the component for the changes to take effect.<br>
 
 e.g., <br>
 

en/developer-docs/docs/develop-components/deploy-mcp-servers/deploy-a-mcp-server.md

@@ -4,7 +4,7 @@ Choreo allows you to create and deploy MCP Server applications in Python and Nod
 
 In this guide, you will:
 
-- Deploy an stdio-based [github-mcp-server](https://github.com/github/github-mcp-server) in Choreo  over SSE (Server-Sent Events) using a `NodeJs` buildpack.
+- Deploy an stdio-based [github-mcp-server](https://github.com/github/github-mcp-server) in Choreo  over SSE (Server-Sent Events) using a `NodeJs` build preset.
 
 ## Prerequisites
 
@@ -33,7 +33,7 @@ To create a mcp server component, follow these steps:
     | **Server Package**       | @modelcontextprotocol/server-github |
     | **Run Command**  | npx -y @modelcontextprotocol/server-github    |
 
-6. Select **NodeJs** as the buildpack.
+6. Select **NodeJs** as the build preset.
 7. Provide component display name, name and description:
 
     !!! info

en/developer-docs/docs/develop-components/develop-a-webhook.md

@@ -49,7 +49,7 @@ To create a Webhook component, follow these steps:
     | **Branch**                    | main               |
     | **Component Path**              | `github-event-to-email-webhook` |
 
-6. Select **Ballerina** as the build pack.
+6. Select **Ballerina** as the build preset.
 7. Provide a display name, a unique name and description for the component.
 8. Click **Create**.
 
@@ -95,7 +95,7 @@ To allow the webhook to read the labels of issues in a specific GitHub repositor
     | **Secret**       | The last webhook secret you configured in [Step 2](#step-2-deploy).|
 
     !!! tip
-        - **Buildpack** specifies the type of build to run depending on the implementation of the component. It converts the integration code into a Docker image that can run on Choreo cloud. If an integration is developed using [WSO2 Integration Studio](https://wso2.com/integration/integration-studio/), select **Micro Integrator** as the buildpack. If an integration is developed using the [Ballerina language](https://ballerina.io), select **Ballerina** as the buildpack.
+        - **Build preset** specifies the type of build to run depending on the implementation of the component. It converts the integration code into a Docker image that can run on Choreo cloud. If an integration is developed using [WSO2 Integration Studio](https://wso2.com/integration/integration-studio/), select **Micro Integrator** as the build preset. If an integration is developed using the [Ballerina language](https://ballerina.io), select **Ballerina** as the build preset.
         - **Project Path** specifies the location of the project to build the component.
 
 7. Under **Which events would you like to trigger this webhook?**, select **Let me select individual events**.