Lint fix

SAP · Feb 18, 2025 · 4abaee0 · 4abaee0
1 parent ebefb45
commit 4abaee0
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 11 deletions.
diff --git a/cmd/cloudFoundryDeploy_generated.go b/cmd/cloudFoundryDeploy_generated.go
diff --git a/documentation/docs/steps/cloudFoundryDeploy.md b/documentation/docs/steps/cloudFoundryDeploy.md
@@ -4,17 +4,19 @@
 
 ### Additional Hints
 
-#### Standard CF deployments 
+#### Standard CF deployments
 
 `deployType` parameter defaults to value `standard`
 This means that CF CLI is called by piper and command `cf push` is run by piper
 
-#### Blue green deployments 
-* With CF CLI 
-    * Blue green deployments are deprecated, but [rolling deployment strategy](https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html) is supported. 
-    * For rolling deployment strategy , set parameter `cfNativeDeployParameters: '--strategy rolling'`
+#### Blue green deployments
+
+With CF CLI
+
+    * Blue green deployments are deprecated, but [rolling deployment strategy](https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html) is supported.
+    * For rolling deployment strategy , set parameter `cfNativeDeployParameters:'--strategy rolling'`
 
-* With [MTA CF CLI Plugin](https://github.com/cloudfoundry-incubator/multiapps-cli-plugin) for MTA applications
+With [MTA CF CLI Plugin](https://github.com/cloudfoundry-incubator/multiapps-cli-plugin) for MTA applications
 
     The Multiapps Plugin offers 2 different strategies:
 
@@ -30,7 +32,6 @@ Parameter `buildTool`  is used to differentiate between MTA and Non MTA applicat
 | **blue-green** | deployTool = mtaDeployPlugin, <br> Uses MTA plugin <br> Piper calls command `cf deploy bgdeploy` | Deprecated. <br> **Alternative:** Rolling deployment strategy by setting parameter <br> `cfNativeDeployParameters = '--strategy rolling'` |
 | **deployDockerImage** | Not supported | 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.
     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.

diff --git a/resources/metadata/cloudFoundryDeploy.yaml b/resources/metadata/cloudFoundryDeploy.yaml
@@ -3,9 +3,9 @@ metadata:
   description: "Deploys an application to Cloud Foundry"
   longDescription: |
     Deploys an application to a test or production space within Cloud Foundry.
-    This step supports two deployment types 
+    This step supports two deployment types:
 
-    * in a standard way with some possible system downtime during app deployment
+    * in a standard way
     * in a zero-downtime manner using a [blue-green deployment approach](https://martinfowler.com/bliki/BlueGreenDeployment.html)
 
     The step achieves this via following deploy tools