Updated PaaS native application document section (#1945)

* Updated PaaS native application document section

* Update docs for new paas-cli

* Described possible shopware paas native event types

* Fix typo

* Update products/paas/shopware/monitoring/watch.md

Co-authored-by: Copilot <[email protected]>

* Update products/paas/shopware/fundamentals/applications.md

Co-authored-by: Copilot <[email protected]>

* Update products/paas/shopware/fundamentals/applications.md

Co-authored-by: Copilot <[email protected]>

* fix/markdown

* fix/small-grammar-issues

---------

Co-authored-by: Patrick Derks <[email protected]>
Co-authored-by: Tom Bojer <[email protected]>
Co-authored-by: Micha Hobert <[email protected]>
Co-authored-by: Copilot <[email protected]>

Author: 5 people

products/paas/shopware/fundamentals/applications.md

@@ -10,17 +10,17 @@ Shopware PaaS Native supports multiple applications within a project, such as en
 
 Each application has its own compute resources, infrastructure, and deployment configuration, so you can tailor each environment to its specific needs.
 
-For instance, you might allocate smaller, hibernating compute instances for staging, while reserving larger, always-on resources for production.
+For instance, you might allocate smaller, hibernating compute instances for staging while reserving larger, always-on resources for production.
 
 ## Creating an Application
 
-Deploy a new application to a project:
+Create a new application to a project:
 
 ```sh
 sw-paas application create
 ```
 
-## Build and Deployments
+## Build your application
 
 To trigger a new build for the application via CLI, use the following command:
 
@@ -34,6 +34,41 @@ This command initiates the build process, packaging your application and prepari
 sw-paas application build logs
 ```
 
+## Update your application
+
+To update your application, you need to run the following command and provide the commit SHA:
+
+```sh
+sw-paas application update
+```
+
+This command initiates the build process, waits until it's done, and runs the deployment for you.
+
+## Deploy a specific build of your application
+
+To create a deployment with a specific build, use the following command:
+
+```sh
+sw-paas application deploy create
+```
+
+It will let you choose which build you want to deploy.
+This is very handy, since you can choose any successful build to deploy: the latest one to bring your change live, or a previous one to fix an issue that arose.
+
+## Deployments management
+
+To list all past deployments:
+
+```sh
+sw-paas application deploy list
+```
+
+To get details about a given deployment:
+
+```sh
+sw-paas application deploy get
+```
+
 ## Plugin Management
 
 Plugin management is done [via Composer](../../../../guides/hosting/installation-updates/extension-managment#installing-extensions-with-composer) because the platform runs in a high-availability and clustered environment.
@@ -112,16 +147,14 @@ cdn.shopware.shop
 
 This configuration ensures that all traffic to your custom domain is routed through the Fastly CDN for optimal performance and caching.
 
-#### Application Updates
+#### Application Deployment
 
 Following domain creation, you must redeploy your application. You can do it by using:
 
 ```sh
-sw-paas application build start
+sw-paas application deploy create
 ```
 
-This process will be automated in future releases.
-
 #### Shopware Configuration
 
 Subsequently, you can configure the domain within Shopware and associate it with a storefront. Status update functionality is currently under development and should be considered a beta feature.

products/paas/shopware/get-started/quickstart.md

@@ -71,14 +71,20 @@ Initialize a new PaaS project:
 sw-paas project create --name "my-shopware-app" --repository "[email protected]:username/repo.git"
 ```
 
-## Step 4: Deploy an Application Instance of the project
+## Step 4: Create and deploy an Application Instance of the project
 
-Deploy your application. Choose your earlier created project:
+Create your application:
 
 ```sh
 sw-paas application create
 ```
 
+Then, deploy your application:
+
+```sh
+sw-paas application deploy create
+```
+
 Monitor the deployment progress:
 
 ```sh

products/paas/shopware/monitoring/watch.md

@@ -42,3 +42,37 @@ Common event types include:
 - `EVENT_TYPE_DEPLOYMENT_FINISHED` - When a deployment completes
 
 The event stream will continue running until you stop it with `Ctrl+C`. All events are displayed in real-time with timestamps and detailed information about what's happening in your project.
+
+## Understanding different Event Types
+
+Events are generally linked to a preceding action.
+Each action is connected to a specific event type, which is emitted when a state change occurs.
+The type of each event is indicated in the output of the `sw-paas watch` command and can help to understand what is happening in your project.
+
+Especially for deployments, the history of the events can be used to understand what happened during a deployment.
+To list all events of a specific deployment, use the following command:
+
+```bash
+sw-paas application deploy get 
+```
+
+The output of the `DEPLOYMENT STATUS HISTORY` shows all events that were emitted during the deployment.
+This contains events from the underlying PaaS infrastructure as well as events from the shop itself.
+
+The following table lists the most common event types and their descriptions:
+
+| Event | Description |
+|-------|-------------|
+| `UNSPECIFIED` | Default or unspecified deployment status |
+| `PENDING` | Deployment is queued and waiting to start |
+| `BASE` | Infrastructure: Base infrastructure components are being deployed |
+| `BASE_FAILED` | Infrastructure: Base infrastructure deployment has failed |
+| `BASE_SUCCESS` | Infrastructure: Base infrastructure deployment completed successfully |
+| `SHOP` | Infrastructure: Shop-specific infrastructure components are being deployed |
+| `SHOP_FAILED` | Infrastructure: Shop infrastructure deployment has failed |
+| `SHOP_SUCCESS` | Infrastructure: Shop infrastructure deployment completed successfully |
+| `DEPLOYING_STORE` | Store: Shopware store application is being deployed |
+| `DEPLOYING_STORE_FAILED` | Store: Shopware store deployment has failed |
+| `DEPLOYING_STORE_SUCCESS` | Store: Shopware store deployment completed successfully |
+| `DEPLOYMENT_SUCCESS` | Complete deployment finished successfully |
+| `DEPLOYMENT_FAILED` | Complete deployment has failed |