From e9e94a2daf4954e8795750e28e079a226de67bb2 Mon Sep 17 00:00:00 2001 From: Hariharan Gandhi <9645184+Hariharan-Gandhi@users.noreply.github.com> Date: Mon, 22 Sep 2025 10:25:25 +0200 Subject: [PATCH 1/3] Add blog post to instance sharing in CF --- docs/ingest-from-cloud-foundry-runtime-f5a7c99.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md b/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md index eadc0dc..723d98a 100644 --- a/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md +++ b/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md @@ -27,7 +27,6 @@ Shipping logs from applications deployed on SAP BTP Cloud Foundry can be configu - We recommend you use one of the Cloud Foundry open source logging libraries \([Java](https://github.com/SAP/cf-java-logging-support)/[NodeJS](https://github.com/SAP/cf-nodejs-logging-support)\) to configure logging within your application. - ### Bind the Application to the Service Instance **Bind the Application Using the Command Line Interface** @@ -52,7 +51,6 @@ Shipping logs from applications deployed on SAP BTP Cloud Foundry can be configu 3. Go to the [Result](ingest-from-cloud-foundry-runtime-f5a7c99.md#loiof5a7c993743c4ee79722479371b90b37__section_gvg_4k4_xyb) section. - ### Share Service Instance Across Different Spaces You can share a single service instance across multiple spaces. Skip this step if you don't need to share a single instance across multiple spaces of the same org. @@ -69,7 +67,7 @@ You can share a single service instance across multiple spaces. Skip this step i > ### Note: > Be careful when deleting service keys. Credentials are invalidated if the service key is deleted, and there is no automated mechanism to track in which user provided services instances the information of a service key is used. - +Please read the blog post that outlines different contexts, tools, options, and best practices for instance sharing in CF: ### Bind the Application to a User Provided Service From cf12a60415097f8c13010c4a54750990b20098c6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=BCrgen=20Walter?= Date: Mon, 22 Sep 2025 13:20:51 +0200 Subject: [PATCH 2/3] Apply suggestion from @juergen-walter --- docs/ingest-from-cloud-foundry-runtime-f5a7c99.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md b/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md index 723d98a..5f34271 100644 --- a/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md +++ b/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md @@ -67,7 +67,7 @@ You can share a single service instance across multiple spaces. Skip this step i > ### Note: > Be careful when deleting service keys. Credentials are invalidated if the service key is deleted, and there is no automated mechanism to track in which user provided services instances the information of a service key is used. -Please read the blog post that outlines different contexts, tools, options, and best practices for instance sharing in CF: +Please read the related [blog post](https://community.sap.com/t5/technology-blog-posts-by-sap/instance-sharing-sap-cloud-logging/ba-p/14179941) that outlines different contexts, tools, options, and best practices for instance sharing in CF ### Bind the Application to a User Provided Service From 436b2de737b5f94fd519f2fd26c309a23e4db087 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=BCrgen=20Walter?= Date: Tue, 23 Sep 2025 09:09:14 +0200 Subject: [PATCH 3/3] Improve wording --- docs/ingest-from-cloud-foundry-runtime-f5a7c99.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md b/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md index 5f34271..cb9d47a 100644 --- a/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md +++ b/docs/ingest-from-cloud-foundry-runtime-f5a7c99.md @@ -67,7 +67,7 @@ You can share a single service instance across multiple spaces. Skip this step i > ### Note: > Be careful when deleting service keys. Credentials are invalidated if the service key is deleted, and there is no automated mechanism to track in which user provided services instances the information of a service key is used. -Please read the related [blog post](https://community.sap.com/t5/technology-blog-posts-by-sap/instance-sharing-sap-cloud-logging/ba-p/14179941) that outlines different contexts, tools, options, and best practices for instance sharing in CF +For more information about different contexts, tools, options, and best practices for instance sharing in Cloud Foundry, see [Instance Sharing - SAP Cloud Logging](https://community.sap.com/t5/technology-blog-posts-by-sap/instance-sharing-sap-cloud-logging/ba-p/14179941). ### Bind the Application to a User Provided Service