Lambda Management

Overview

The Lambda Management service provides a REST interface to read the configurations of lambda enrichers. Using the Lambda Management service, you can retrieve the specified lambda enrichers by their identifiers.


API Reference

/{tenant}/configurations

/{tenant}/configurations

get

Gets all configuration for its owner. The hybris.configuration_view scope is required.

/{tenant}/configurations/{key}

get

Gets single configuration entry for given key within owner tenant. The hybris.configuration_view scope.

delete

Deletes single configuration entry for given key within owner tenant. The hybris.configuration_manage scope is required.

put

Inserts single configuration entry for given key within owner tenant. The hybris.configuration_manage scope is required.

/lambdas

/lambdas/{lambdaId}

get

Gets lambda details by its lambda id, regardless if it is draft or deployment. To get data hybris.profile_lambda_view scope is required.


Get lambda enricher details

The Lambda Management service provides an endpoint that allows you to get the details of a given lambda enricher.

cURL command pattern

curl -X GET -H "Authorization: Bearer Access_token" 'https://api.beta.yaas.io/hybris/lambda-management/v2/lambdas/lambdaId'

Command parameters

  • Headers
    • Authorization: A valid Bearer access_token
  • URI parameters
    • lambdaId: An identifier in the UUID format. It is unique and constant for each combination of a given enricherID, lambda enricher version, and lambda enricher type.

Example of a GET request with real data

 curl -X GET -H "Authorization: Bearer 001-ad2b1327-8888-4ce4-b2cc-d64a9bc4932e" 'https://api.beta.yaas.io/hybris/lambda-management/v2/lambdas/dca08b12-4180-404d-943f-5ee0d5bad630

Response

A response with a status code of 200 returns the details of the requested lambda enricher.


Glossary

TermDescription
authorizationThe process of determining whether a given microservice has permission to gain consent.
consentPermission to access (read, write) specific profile data, for example, permission to read or write an age estimation or a physical address. A consumer and a tenant can grant and revoke consent for subsets of their respective data.
consent classA string alias, defined by developers, that references a set of profile data (also called "schemas") for which consent can be granted and revoked. This string is exposed to consumers and tenants as a reference through which they control consent. For example, the consent class "Purchases" might reference a set of data that includes items purchased, purchase dates, and purchase prices. Toggling consent for "Purchases" would enable and disable consent for that entire set of data.
consent referenceA unique, randomized string that serves as a passcode to decrypt data associated with one or more schemas. Various service calls require a consent reference.
consumerThe end user whose actions yield profile data in the graph. A profile describes a single consumer.
contextData that affects the state of the graph. This data can be collected from consumer-triggered events or from third-party sources such as weather stations.
context adapterA microservice that receives data and, optionally, adapts it for entry into the graph. For example, a context adapter can adapt address data by adding a ZIP code and normalizing the street labels (for example, changing "St" to "Street"). The context adapter then passes the data through the Context service, which caches it so that enrichers can subsequently persist the data in the graph.
context repositoryA temporary cache for adapted context data, before enrichers process the adapted data further and persist it in the graph.
context serviceAn internal microservice that manages the insertion of, and the retrieval of, context data in the Context Repository.
encryption keyA unique, randomized string used to encrypt and decrypt specific data in the graph. Each data element is encrypted with a different encryption key. Decryption, using this key, is required to access, view, and alter the data.
enricherA microservice that retrieves data from the Context Repository and/or Graph, possibly alters or extends it, and then persists data in the graph. An enricher can interpret data points, or sets of data points, to yield new data to persist. For example, an enricher can interpret purchasing data and contemporaneous weather station data to yield new data indicating that the consumer is a rainy-day shopper.
graphThe database that stores profile data as nodes, edges, and properties, and allows semantic queries.
identityOne of many independent units of data used to identify a unique profile, such as an email address, browser type, or version.
profileData about a single consumer, collected and derived from events that are triggered by, or are logically associated, with that consumer.
schemaA string representation of a path in the graph that represents an abstraction, rather than a concrete instance, of a particular data structure.
tenantA registered entity with a shared commercial goal that subscribes to SAP Hybris Profile services and packages to reach that goal. A tenant can also develop and contribute enrichers and context adapters to the SAP Hybris Profile suite. Within YaaS, a tenant is a project.


  • Send feedback

    If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.

  • Get Help

    Use our private help channel. Receive updates over email and contact our specialists directly.

  • hybris Experts

    If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.