From f1d0dcce3dbb1e85c7bf7fd44f7f7596244bdd3b Mon Sep 17 00:00:00 2001 From: Ashly Mathew Date: Mon, 24 Feb 2025 11:53:44 +0100 Subject: [PATCH] Add note about docker deployments --- documentation/docs/steps/cloudFoundryDeploy.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/documentation/docs/steps/cloudFoundryDeploy.md b/documentation/docs/steps/cloudFoundryDeploy.md index dd7dbd12c6..b5c95130c8 100644 --- a/documentation/docs/steps/cloudFoundryDeploy.md +++ b/documentation/docs/steps/cloudFoundryDeploy.md @@ -37,14 +37,13 @@ This table compares deployment strategies for MTA and Non-MTA applications. | | **deployDockerImage not supported** | **deployDockerImage supported**
Docker credentials can only be provided as Jenkins environment variable. | !!! note - Due to [an incompatible change](https://github.com/cloudfoundry/cli/issues/1445) in the Cloud Foundry CLI, multiple buildpacks are not supported by this step. +- Due to [an incompatible change](https://github.com/cloudfoundry/cli/issues/1445) in the Cloud Foundry CLI, multiple buildpacks are not supported by this step. If your `application` contains a list of `buildpacks` instead of a single `buildpack`, this will be automatically re-written by the step when blue-green deployment is used. - -!!! note - Cloud Foundry supports the deployment of multiple applications using a single manifest file. +- Cloud Foundry supports the deployment of multiple applications using a single manifest file. This option is supported with project "Piper". In this case, define `appName: ''` since the app name for the individual applications has to be defined via the manifest. You can find details in the [Cloud Foundry Documentation](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#multi-apps) +- Recommended way to do **docker image deployments** is via [Kubernetes Piper step](https://github.wdf.sap.corp/pages/ContinuousDelivery/piper-doc/steps/kubernetesDeploy/).This step is not capable of deploying docker images built in the same pipeline using other piper steps[i.e., kanikoExecute]. ## Prerequisites