Skip to Content
⚠️ Action required: DeltaTwin API has been updated to v2.1. Please update your deltatwin-cli. Read our technical notes for details.
DocumentationRelease Notes1.7.0

Key features in v1.7.0

DESP Tenancy service integration & Namespace concept

DeltaTwin® now integrates with the DestinE Platform Tenancy service, that enables a group of DestinE users to access and manage upgraded platform resources and ease the cooperation between them.

In this scope, DeltaTwin® is introducing the concept of Namespaces.

A namespace is an isolated collaborative environment shared among the members of a DESP Tenancy project. This makes it possible for a group of users — typically an organisation — to share DeltaTwin® resources and work together efficiently.

Each user is automatically assigned to a namespace at login:

  • Free DestinE users get a private namespace with default resources (10 daily runs, 20 GB storage, 5 schedulers).
  • Tenancy project members share a common namespace with upgraded, on-demand resources ( daily runs, storage and schedulers).

Within a namespace, all members can view, update, and delete shared runs, DeltaTwin® components, artifacts, and schedulers. Data stored in a namespace is fully isolated from other namespaces.

As a consequence, DeltaTwin® component names are now only required to be unique within a namespace, rather than across the entire service. Two different namespaces can therefore contain components with the same name.

For more details, see the Namespace concept page.

Secret inputs support for local run

Users can now pass inputs of type secret directly to the deltatwin run start_local command, eliminating the need for workarounds when running DeltaTwin® components locally.