Problem

The tenant delivery APIs require an activated Akamai configuration that map the specific tenant URLs to the right service endpoints / folders on Akamai NetStorage. When a tenant is freshly on-boarded, this configuration is not yet available since the activation of the tenant specific configuration takes up to 30 minutes on Akamai. During that time, the ootb site (preview) is not accessible which gives a bad "first use experience".

Solution:

We could pre-create and activate Akamai configurations for tenants that we will onboard in the future. With this, the tenant can directly use the delivery APIs and ootb Site.

High level Approach:

To implement this, the ECS needs to know the actual tenant IDs and corresponding edgeToken values of those tenants to be on-boarded in the future (since this ID is needed to create the Akamai config).

To get to those values, the ECS could post an Array of edgeToken values to TRS, and the TRS serves back the mappign of those token to tenant IDs for future tenants. ECS can than pre-create the corresponding configuration on Akamai. During onboarding, the TRS would already set the edgeToken value in the TRS JSON record, such that ECS has actually no longer work to do , since the corresponding configuration is already active. Details to be sorted out ....

ZH Discussion: https://github.ibm.com/DX/om-backlog/issues/1028