From 82f6d58735aff78999129a76c59d59632eaf2343 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tilo=20K=C3=B6rner?=
 <70266685+tiloKo@users.noreply.github.com>
Date: Mon, 22 Jul 2024 11:57:08 +0200
Subject: [PATCH] Update abapAddonAssemblyKitCheck.yaml (#4988)

* Update abapAddonAssemblyKitCheck.yaml

remove bullet points as they are not rendered together with markdown

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

diff --git a/cmd/abapAddonAssemblyKitCheck_generated.go b/cmd/abapAddonAssemblyKitCheck_generated.go
index e153d4e165..73090511f1 100644
--- a/cmd/abapAddonAssemblyKitCheck_generated.go
+++ b/cmd/abapAddonAssemblyKitCheck_generated.go
@@ -71,9 +71,9 @@ func AbapAddonAssemblyKitCheckCommand() *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>
-  <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>
+  [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)
+  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)
+  The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps
 </ul>
 <br />
 For logon to AAKaaS you can either provide a credential with basic authorization (username and password) or two secret text credentials containing the technical s-users certificate (see note [2805811](https://me.sap.com/notes/2805811) for download) as base64 encoded string and the password to decrypt the file
diff --git a/resources/metadata/abapAddonAssemblyKitCheck.yaml b/resources/metadata/abapAddonAssemblyKitCheck.yaml
index 19842737b1..a7c9859bd5 100644
--- a/resources/metadata/abapAddonAssemblyKitCheck.yaml
+++ b/resources/metadata/abapAddonAssemblyKitCheck.yaml
@@ -3,9 +3,9 @@ metadata:
   description: This step calls AAKaaS to check the validity of the Addon Product Modelling.
   longDescription: |
     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>
+      [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)
+      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)
+      The semantic versions are resolved and stored into the piper commonPipelineEnviroment for usage of subsequent pipeline steps
     </ul>
     <br />
     For logon to AAKaaS you can either provide a credential with basic authorization (username and password) or two secret text credentials containing the technical s-users certificate (see note [2805811](https://me.sap.com/notes/2805811) for download) as base64 encoded string and the password to decrypt the file