From 460192d92c3fbb24be3dc6a86a4be5216dba0a78 Mon Sep 17 00:00:00 2001 From: i325261 Date: Wed, 16 Oct 2024 11:18:20 +0200 Subject: [PATCH] added documentation --- .../content/en/docs/usage/resources/capapplicationversion.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/content/en/docs/usage/resources/capapplicationversion.md b/website/content/en/docs/usage/resources/capapplicationversion.md index e766786..6e8553b 100644 --- a/website/content/en/docs/usage/resources/capapplicationversion.md +++ b/website/content/en/docs/usage/resources/capapplicationversion.md @@ -42,6 +42,8 @@ spec: > The `CAPApplicationVersion` resource is meant to be immutable - it's spec should not be modified once it is deployed. This is also prevented by our web-hooks which we recommend to always keep active (default). +> By default, credentials (from secrets) required to access SAP BTP services are automatically provided as the `VCAP_SERVICES` environment variable across all workloads. However, this behavior can be changed to use volume mounts by setting the annotation `sme.sap.com/use-volume-mount: "true"` on the `CAPApplicationVersion` resource. When this annotation is set, the `SERVICE_BINDING_ROOT` environment variable will be injected into all the workloads, pointing to the secret path and overriding any user-defined values, if specified. + ### Workloads with `deploymentDefinition` ```yaml @@ -364,4 +366,4 @@ spec: > > The supported configurations is kept minimal intentionally to keep the overall API simple by considering commonly used configurations. -> Note: For `initContainers` nearly the same environment variables as the main container are made available including VCAP_SERVICES environment. \ No newline at end of file +> Note: For `initContainers` nearly the same environment variables as the main container are made available including VCAP_SERVICES environment.