What's New
- Destination-based configuration for Audit Log NG —
create_client() in sap_cloud_sdk.core.auditlog_ng now accepts three new keyword arguments: destination_name, destination_instance, and fragment_name. When provided (or when the defaults destination_name="AuditLogV3_Destination" / destination_instance="default" are in effect), the function resolves endpoint, deployment_id, and namespace automatically from the named SAP Destination at subaccount level, eliminating the need to pass these values explicitly in SPII-based deployments.
Improvements
create_client() now documents three mutually exclusive configuration paths evaluated in order: explicit config object → destination-based resolution → explicit keyword arguments (endpoint, deployment_id, namespace).
deploymentRegion destination property is accepted as a fallback for deployment_id when deploymentId is absent or empty.
- Destination import is lazy, so importing
auditlog_ng in environments without the destination module installed continues to work without errors.
- User guide (
auditlog_ng/user-guide.md) updated with a new Destination-based configuration section, parameter tables, and usage examples.
- Unit tests for
create_client() extended with a TestCreateClientFromDestination suite covering happy path, deploymentRegion fallback, missing required properties, and regression tests for the existing explicit-args path.
starlette dev dependency bumped from 1.0.0 to 1.3.1.
Contributors
@betinacosta, @cassiofariasmachado, @NicoleMGomes