Configuration
Per-environment settings without per-environment code — profiles, layered configuration, and bindings resolved from the platform at start-up.
Overview
@sap/cds Resolves layered configuration through cds.env — profiles, environment and service bindings merged into one view.
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 runtimeSAP BTP, Kyma runtimeA fully managed Kubernetes runtime on SAP BTP, based on the open-source project Kyma, where extensions to SAP solutions run as containerised microservices and serverless Functions.sap official, btp 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 togglesFeature togglesTurning behaviour on and off per tenant or per user at runtime, without redeploying, and knowing which toggles are live. System-level switches for delivered objects and runtime flags for unfinished features share the name.SAP and community, narrow by design for behaviour per tenant or user and secrets rotationSecrets rotationRotating credentials a running service depends on — service keys, destination credentials, API tokens — without downtime and without redeploying. Distinct from storing secrets, which the platform handles.SAP only for credentials.
No community artifact is documented here.
On an ABAP system configuration is mostly values a program reads at runtime instead of hard-coding them: parameters, selection ranges and mappings kept in TVARVC or a custom table, some of them maintained directly in production without a transport.
Table TVARVC holds variables for report variants, maintained per client with transaction STVARV; changing a value there changes every variant that uses it.
Not covered: At variants. SAP documents TVARVC as a source of values for selection screens in background processing; reading typed values, structures and tables from program code is not part of it, and that is where the ABAP libraries sit.
Libraries that keep parameters and constants out of ABAP code, as wrappers around TVARVC or replacements for it, such as abaKabaKA beta library for ABAP constants that lets each program register its own source, a custom table or CSV, XML or JSON content from a URL, standard text, server file or remote system, rather than one shared table.independent, abap and aqoaqoA library for defining ABAP application options as a structure or class, with change history, transport integration and a maintenance UI generated from that description, instead of SM30 tables or STVARV.independent, abap, and config-managementconfig-managementKeeps the theme, UI5 bootstrap source, custom CSS and Content-Security-Policy of an abap2UI5 page in database tables instead of in code, with a popup app to edit them.community org, abap from abap2UI5 addonsabap2UI5-addonsmaintains 21 entriesindependent, which keeps the theme, CSS and Content-Security-Policy settings of an abap2UI5 page in database tables.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:configuration- JSON
- /capabilities/configuration.json
- MCP
- Connecting an agent