Configuration

Per-environment settings without per-environment code — profiles, layered configuration, and bindings resolved from the platform at start-up.

Overview

SAP SHIPS

Node.js →

@sap/cds Resolves layered configuration through cds.env — profiles, environment and service bindings merged into one view.

Java →

com.sap.cds:cds-feature-cloudfoundry A CAP Java feature that reads the environment variables of SAP BTP, Cloud Foundry at start-up and resolves bound service credentials from them, so the other features find their bindings.

com.sap.cds:cds-feature-k8s A CAP Java feature that reads the service bindings the SAP BTP Operator writes on Kyma runtime at start-up, replacing the removed cds.environment.k8s property.

com.sap.cds:cds-services-bom Configures applications through Spring Boot's externalized configuration and CDS properties, with a production profile that switches a set of property defaults, such as disabled mock users, at once.

Not covered: On Node.js it stops at process start: cds.env loads its sources on first use, credentials are filled from the process environment when the process starts, and a value assigned in code changes the running program only. A value that has to change while the service runs is another concern, feature toggles for behaviour per tenant or user and secrets rotation for credentials.