From 33c31e5f500f3728620ab21537dd1066c89fef6c Mon Sep 17 00:00:00 2001
From: tiloKo <70266685+tiloKo@users.noreply.github.com>
Date: Mon, 15 Apr 2024 16:06:00 +0200
Subject: [PATCH] dummy change in yaml

---
 cmd/abapAddonAssemblyKitCheck_generated.go        | 3 +--
 resources/metadata/abapAddonAssemblyKitCheck.yaml | 3 +--
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/cmd/abapAddonAssemblyKitCheck_generated.go b/cmd/abapAddonAssemblyKitCheck_generated.go
index 1027325870..e153d4e165 100644
--- a/cmd/abapAddonAssemblyKitCheck_generated.go
+++ b/cmd/abapAddonAssemblyKitCheck_generated.go
@@ -70,8 +70,7 @@ func AbapAddonAssemblyKitCheckCommand() *cobra.Command {
 	var createAbapAddonAssemblyKitCheckCmd = &cobra.Command{
 		Use:   STEP_NAME,
 		Short: "This step calls AAKaaS to check the validity of the Addon Product Modelling.",
-		Long: `This step does the following:
-<ul> 
+		Long: `This step does the following:<ul>
   <li>[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml)</li>
   <li>A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules)</li>
   <li>The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps</li>
diff --git a/resources/metadata/abapAddonAssemblyKitCheck.yaml b/resources/metadata/abapAddonAssemblyKitCheck.yaml
index dfa6eb90f2..19842737b1 100644
--- a/resources/metadata/abapAddonAssemblyKitCheck.yaml
+++ b/resources/metadata/abapAddonAssemblyKitCheck.yaml
@@ -2,8 +2,7 @@ metadata:
   name: abapAddonAssemblyKitCheck
   description: This step calls AAKaaS to check the validity of the Addon Product Modelling.
   longDescription: |
-    This step does the following:
-    <ul>
+    This step does the following:<ul>
       <li>[The Addon Product Modelling](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#add-on-descriptor-file) is read from the <b>addonDescriptorFileName</b> (e.g. addon.yml)</li>
       <li>A connection to AAKaaS (Addon Assembly Kit as a Service) is established and the Addon Product Modelling is transfered for detailed [checks](https://www.project-piper.io/scenarios/abapEnvironmentAddons/#versioning-rules)</li>
       <li>The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps</li>