From c606b98d5d070a5520d1cbbca2209d45f0ea6c4c Mon Sep 17 00:00:00 2001 From: Bas de Jong Date: Wed, 11 Dec 2024 11:25:07 +0100 Subject: [PATCH] Update lifetime-deployment-api-v2.final.md add unsupported scenario's for manual intervention scenario's. --- src/ref/apis/auto/lifetime-deployment-api-v2.final.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/ref/apis/auto/lifetime-deployment-api-v2.final.md b/src/ref/apis/auto/lifetime-deployment-api-v2.final.md index 66553330a..af849cd2a 100644 --- a/src/ref/apis/auto/lifetime-deployment-api-v2.final.md +++ b/src/ref/apis/auto/lifetime-deployment-api-v2.final.md @@ -329,6 +329,16 @@ Returns a link where the binary file for a given application version can be down ### /deployments/ +This endpoint allows you to perform operations on deployments. Please note that there are a few unsupported scenario's. Currently it is not possible to: + +- Set/edit database catalogs +- Perform actions when a deployment has BPT process impact + +In these cases,the deployment will be paused, and the status will be: "needs_user_intervention", which forces you to open the ongoing deployment in lifetime and perform these actions manually. +Please note that in order to pause the deployment when a database catalog needs to be set, the Service Account running the deployment must have rights on at least 1 database catalog. Otherwise the deployment will not pause to perform the manual intervention. + + + #### POST { #post-deployments } ##### Description: