Merge branch 'development' into pr/10696

Author: ConnorLand

_scripts/removeUnusedAttachments.py

@@ -61,6 +61,6 @@ def dirWalk(start, globPattern="**/*"):
             break
     # Delete files that are in dirList2 and not in the attachment list
     if deleteFlag is True:
-        # Make sure that it is not a directory
-        if pathlib.Path.is_file(file):
+        # Make sure that it is not a directory and not a .drawio file
+        if pathlib.Path.is_file(file) and not file.name.endswith('.drawio'):
             pathlib.Path.unlink(file)

content/en/docs/control-center/security/private-connectivity/_index.md

@@ -15,6 +15,10 @@ This feature is in Public Beta. For more information, refer to [Release Status](
 
 The **Private Connectivity** page allows you to view and manage your company's Private Connectivity assets: networks, agents, resources, and connections.
 
+{{% alert color="info" %}}
+If you cannot access the **Private Connectivity** page, contact your CSM or Mendix Support.
+{{% /alert %}}
+
 ## Use Cases
 
 Many apps running on Mendix Cloud have integrations with external resources, such as databases, services, and other applications. Some of these resources are public, accessible via the public internet. Others are running on your internal networks, either on-premises or on cloud infrastructure, as PaaS/SaaS. You can connect to these resources over the public internet as well, [securing](/developerportal/deploy/securing-outgoing-connections-from-your-application/) them with HTTPS, a reverse proxy, and client certificates. This scenario requires you to expose your internal resource to the public internet. However, due to security, compliance, or legacy reasons, not everyone wants to or is able to do this. 

content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md

@@ -40,8 +40,8 @@ On the **Networks** tab of the **Private Connectivity** page, you can see all th
 
     * **Details**    
     <!-- * **Add DNS** -->
-	* **Add Agent**
-	<!-- * **Edit**
+    * **Add Agent**
+    <!-- * **Edit**
 	* **Delete** -->
 
 ### Adding a Network {#private-connectivity-networks-add}
@@ -71,7 +71,7 @@ To view and edit an existing network, follow these steps:
     * **Network** – The name you gave to the network. This field is editable.
     * **Network ID** – The internal ID of your network. You can copy this if, for example, you want to provide it in a support ticket for any issues with the network.
     * **External Agents** – A list of all external agents that run on your own internal infrastructure, and that have access to the network.    
-	  This field also displays the status of each agent.
+      This field also displays the status of each agent.
     <!-- * **DNS Details** – A list of domains for which you have [configured DNS](#private-connectivity-networks-dns). -->
     * **Environment Details** – A list of app environments that are using the network to connect to a resource, as well as the environment's status.
     <!-- * **Show Logs** – This allows you to see [the flow logs](https://tailscale.com/kb/1219/network-flow-logs) for your network. They can help you troubleshoot issues with connectivity on your network. -->
@@ -306,7 +306,7 @@ The page displays the following information for each resource:
 * **Status** – The status of the resource. This can be one of the following:
 
     * Enabled – Technical Contacts can request connections to the resource.
-	* Disabled – Technical Contacts cannot request connections to the resource.
+    * Disabled – Technical Contacts cannot request connections to the resource.
 
 * **Environments** – The number of app environments on Mendix Cloud that have an approved connection to the resource.
 
@@ -329,8 +329,8 @@ To view and edit a resource, follow these steps:
     * **Network** – The name of the network to which the agent exposing the resource is connected.
     * **Status** – The status of the resource. This can be one of the following:
 
-	    * **Enabled** – Users can request connections to the resource.
-	    * **Disabled** – Users cannot request connections to the resource.
+        * **Enabled** – Users can request connections to the resource.
+        * **Disabled** – Users cannot request connections to the resource.
 
     * **Environment Details** – A list of app environments that have an approved connection to the resource.
 
@@ -408,8 +408,8 @@ On the **Connections** tab of the **Private Connectivity** page, you can see all
 * **Status** – The status of the connection. This can be one of the following:
 
     * **Pending** – The connection was requested, but not yet approved. The app environment cannot connect to the resource using this connection.
-	* **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
-	* **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
+    * **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
+    * **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
 
     For details on how Technical Contacts request connections for a specific environment, refer to [Connecting to External Resources](/developerportal/deploy/connecting-to-external-resource/).
 
@@ -422,14 +422,14 @@ To view an existing connection, follow these steps:
 
     * **Request Details** – The details of the connections request:
 
-	    * **Name** – The name of the user that requested this connection.
-	    * **Status** – The status of the connection request. This can be one of the following:
+        * **Name** – The name of the user that requested this connection.
+        * **Status** – The status of the connection request. This can be one of the following:
 
-		    * **Pending** – The connection was requested, but not yet approved. The app environment cannot connect to the resource using this connection.
-		    * **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
-		    * **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
+            * **Pending** – The connection was requested, but not yet approved. The app environment cannot connect to the resource using this connection.
+            * **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
+            * **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
 
-	    * **Date** – The date and time when the connection was requested.
+        * **Date** – The date and time when the connection was requested.
 
     * **App** – The name of the app for the connection.
     * **Environment** – The name of the environment for the connection.

content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md

@@ -30,6 +30,10 @@ To create a backup archive of a licensed app, follow these steps:
 4. Click **Create Backup**.
 
     {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backupoptions.png" class="no-border" >}}
+    If backup creation overlaps with an RDS backup or maintenance window, the backup may fail immediately. The **Comment** column for the failed backup provides additional details.
+
+   {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backup-rds-window-failure.png"  >}}
+
 
 Once you have created a backup archive, you can download it by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) then selecting **Download**. For more information, see [Downloading a Backup](/developerportal/operate/download-backup/).
 

content/en/docs/deployment/mendix-cloud-deploy/change-plan.md

@@ -157,7 +157,6 @@ After scheduling, once the plan change process starts:
 2. If the request fails required validations, the status changes to **Ineligible**.
 3. If the request passes all required validations, the status progresses to **Completed** (if successful) or **Failed** (if an execution error occurs).
 
-
 {{% alert color="info" %}}
 After a plan change is applied, you cannot change to a new plan for the same environment for the next 6 hours.
 {{% /alert %}}

content/en/docs/deployment/mendix-cloud-deploy/environments-details.md

@@ -599,4 +599,4 @@ One custom service is available: Mendix Event Broker. This service is required t
 
 ### Enabling Custom Services
 
-Custom services are only available if the app's Technical Contact has enabled them. The custom services are enabled or disabled separately for each environment of each app. For more information, see [Services](/developerportal/deploy/environments/#services) in the *Environments* documentation.
+Custom services are only available if the app's Technical Contact has enabled them. The custom services are enabled or disabled separately for each environment of each app. For more information, see [Services](/developerportal/deploy/environments/#services) in the *Environments* documentation.

content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md

@@ -18,23 +18,23 @@ With ZDT, Mendix Cloud intelligently manages the deployment process, ensuring yo
 
 To leverage the benefits of zero-downtime deployment, your Mendix application and deployment environment must meet the following criteria:
 
-* **Mendix runtime version** – Must be running on Mendix Runtime version 10.24 or higher.
+* **Mendix runtime version** – Must be running on Mendix Runtime version 10.24 or above.
 * **Application instances** – The application must be configured to run with a single runtime instance.
 * **Change type** – The deployment must involve only [configuration-level changes](/developerportal/deploy/zero-downtime/#zdt-application).
 * **Deployment platform** – Must be deployed on Mendix Cloud(Kubernetes).
 
 {{% alert color="info" %}}
-No special setup is required to enable ZDT. When your application and deployment meet these prerequisites, ZDT is automatically applied for eligible changes and can be controlled directly by Technical Contacts through the [Environment Settings](/developerportal/deploy/environments/#environment-settings).
+No special setup is required to enable ZDT. When your application and deployment meet these prerequisites, ZDT is automatically available for eligible changes.
 {{% /alert %}}
 
 ## How Zero-Downtime Deployment Works
 
 <!-- Diagram provided by the deployment team. Contact the team for updates or questions  -->
 {{< figure src="/attachments/deployment/mendix-cloud-deploy/zero-downtime/zdt-process-success-flow.png" alt="Sequence diagram illustrating the Zero-Downtime Deployment process, showing the Technical Contact initiating deployment, Mendix Cloud starting a new app version in the background while the current version serves users, the new version preparing configuration and reporting ready, Mendix Cloud gracefully stopping the old version, and finally directing traffic to the new version without user interruption." >}}
 
-When an eligible configuration change is deployed with ZDT enabled, Mendix Cloud orchestrates the following steps:
+When an eligible configuration change is deployed with ZDT, Mendix Cloud orchestrates the following steps:
 
-1. **Initiate deployment** – The Technical Contact triggers deployment with **Deploy without Downtime** enabled in Mendix Cloud.
+1. **Initiate deployment** – The Technical Contact triggers deployment with **Deploy without Downtime** in Mendix Cloud.
 2. **Current version active** – The existing application version continues to serve all user traffic without interruption.
 3. **New version spin-up** – A new instance of your application starts, adding the updated configuration, in the background. This new version prepares its configuration.
 4. **Health check & readiness** – Once the new instance is fully operational and passes all internal health checks, it reports its readiness to Mendix Cloud.
@@ -46,10 +46,10 @@ When an eligible configuration change is deployed with ZDT enabled, Mendix Cloud
 
 By default, this option is off. In this state, your app will use the standard restart process during deployment. This default setting ensures stability and compatibility with existing application behavior.
 
-Technical Contacts can decide whether to attempt a zero-downtime deployment by selecting the **Deploy without downtime** option on the **Other Options** tab when [deploying a package](/developerportal/deploy/environments/#deploy-wizard). If you enable this option, Mendix Cloud will attempt a zero-downtime deployment, if your environment meets eligibility criteria.
+Technical Contacts can decide whether to attempt a zero-downtime deployment by selecting the **Deploy without downtime** option on the **Other Options** tab when [deploying a package](/developerportal/deploy/environments/#deploy-wizard). If you select this option, Mendix Cloud will attempt a zero-downtime deployment.
 
 {{% alert color="info" %}}
-When a Technical Contact enables ZDT, the Cloud Portal displays a reminder to review any custom **before-shutdown** or **after-startup** microflows. This is crucial to ensure these microflows won’t cause conflicts during periods when two versions of your application might be running concurrently.
+When a Technical Contact selects ZDT, the Cloud Portal displays a reminder to review any custom **before-shutdown** or **after-startup** microflows. This is crucial to ensure these microflows won’t cause conflicts during periods when two versions of your application might be running concurrently.
 {{% /alert %}}
 
 ### When ZDT Applies {#zdt-application}
@@ -70,15 +70,14 @@ During these types of updates, Mendix Cloud performs the deployment in a way tha
 
 Zero-downtime deployment will not apply under the following conditions:
 
-* Mendix Runtime version is less than 10.24
+* Mendix Runtime versions below 10.24
 * Application runs with more than one runtime instance
 * Upgrading to a new Mendix Runtime version
 * Deploying a new MDA (application model update)
 * Changes involve database structure updates
     {{< figure src="/attachments/deployment/mendix-cloud-deploy/zero-downtime/zdt-scaling-process.png" >}}
 
-For these scenarios, the Cloud Portal will display the standard restart message before deployment:
-{{< figure src="/attachments/deployment/mendix-cloud-deploy/zero-downtime/zdt-scaling-messages.png" >}}
+For these scenarios, the Cloud Portal will display the standard restart message before deployment.
 
 ## Expected ZDT Behavior
 
@@ -102,7 +101,7 @@ For eligible environments, the **Deploy Wizard** clearly indicates that the upco
 
 ### First Deployment
 
-When you deploy an application on Mendix Runtime 10.24 or higher for the very first time, the environment is automatically prepared for future zero-downtime deployments. This initial deployment behaves like a regular one, but from the next deployment onward, eligible configuration changes can be applied without downtime.
+When you deploy an application on Mendix Runtime 10.24 or above for the very first time, the environment is automatically prepared for future zero-downtime deployments. This initial deployment behaves like a regular one, but from the next deployment onward, eligible configuration changes can be applied without downtime.
 
 ### During a Zero-Downtime Deployment Failure
 

content/en/docs/deployment/mx-azure/mx-azure-monitor.md

@@ -160,4 +160,4 @@ rate(
 
 * Trigger when the reduced value is above **0.1**.
 
-This alert fires when the application consumes more than 0.1 CPU core.
+This alert fires when the application consumes more than 0.1 CPU core.

content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md

@@ -108,11 +108,11 @@ You can specify the following options:
     For example, setting this to **50%** will switch all clients to the updated app version once 50% of all replicas are running the updated version. If not otherwise specified, 50% is used as the default value. This option is only used if the strategy **type** is set to **PreferRolling**.
 * **rollingUpdate** - Specifies parameters for rolling updates if the Operator is able to perform the update without a restart. These parameters are used as Kubernetes [rollingUpdate](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment) parameters:
     * **maxSurge** – Specifies an absolute or percentage value for how many additional replicas can be added during the deployment process.
-      * For apps with 1 replica, the default value is **1**, to run an updated (replacement) replica in addition to the current replica, and prevent any downtime when possible.
-      * For apps with 2 or more replicas, the default value is **0**, so that no additional replicas are added during the rollout process, and instead existing replicas are stopped to avoid using additional cluster resources.
+        * For apps with 1 replica, the default value is **1**, to run an updated (replacement) replica in addition to the current replica, and prevent any downtime when possible.
+        * For apps with 2 or more replicas, the default value is **0**, so that no additional replicas are added during the rollout process, and instead existing replicas are stopped to avoid using additional cluster resources.
     * **maxUnavailable** – Specifies an absolute or percentage value for how many replicas can be stopped to be replaced with updated versions during the rollout process. Increasing this value speeds up the rollout process, but can cause performance issues.
-      * For apps with 1 replica, the default value is **0**, to ensure that at least one replica is running, and prevent downtime.
-      * For apps with 2 or more replicas, the default value is **1**, so that at most one replicas would be stopped during the update process.
+        * For apps with 1 replica, the default value is **0**, to ensure that at least one replica is running, and prevent downtime.
+        * For apps with 2 or more replicas, the default value is **1**, so that at most one replicas would be stopped during the update process.
 
 ## Configuring Pod Disruption Budget parameters in Standalone Environments {#pod-disruption-budget-in-standalone}
 
@@ -143,9 +143,9 @@ spec:
 You can specify the following options:
 
 * **maxUnavailable** – Specifies an absolute or percentage value for how many replicas can be stopped if Kubernetes needs to evict them from a node.
-  * For apps with 2 or more replicas, the default value is **1** and means that at most 1 replica can be stopped, and that Kubernetes needs to wait until a replacement replica becomes available. Increasing this value speeds up the rollout process, but can cause performance issues.
+    * For apps with 2 or more replicas, the default value is **1** and means that at most 1 replica can be stopped, and that Kubernetes needs to wait until a replacement replica becomes available. Increasing this value speeds up the rollout process, but can cause performance issues.
 * **minAvailable** – Specifies an absolute or percentage value for how many replicas need to be remain available if Kubernetes needs to evict them from a node. Increasing this value slows down the rollout process, but ensures that less replicas can be disrupted.
-  * For apps with 1 replica, the default value is **1** to ensure that at least one replica is always available, and prevent downtime.
+    * For apps with 1 replica, the default value is **1** to ensure that at least one replica is always available, and prevent downtime.
 
 {{% alert color="warning" %}}
 Kubernetes doesn't allow specifying values for both `maxUnavailable` and `minAvailable`, and specifying values for both of them will [result in an error](https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget).

content/en/docs/marketplace/platform-supported-content/modules/document-generation/_index.md

@@ -71,4 +71,4 @@ The PDF document generation service does not store pages or documents at any tim
 
 ### Dependencies
 
-* [Combo Box](https://marketplace.mendix.com/link/component/219304) widget
+* [Combo Box](https://marketplace.mendix.com/link/component/219304) widget