Contexto

Cada entidad dentro de DTZ necesita tener un contexto padre. Esto representa la estructura organizativa para alojar una entidad, permitir el control de acceso y proporciona contabilidad y facturación. Every user has by default attached to its session. So whenever a user is logged in, regardless of the method (apikey, oauth, etc.) the session already has a context attached to it.

flowchart LR 
  uid[Identidad de usuario] -- "tiene acceso" --> context
  subgraph context
  Context[Núcleo del contexto] -- "posee" --> Objectstore[Almacenamiento de objetos]
  Context -- "posee" --> Containers[Contenedores]
  Context -- "posee" --> Rss2Email[RSS a correo]
  Context -- "posee" --> E@{ shape: processes, label: "Otros servicios"}
  end

The current context is always shown in the title bar on the top left.

Changing the context can be achieved by selecting the new context from the drop-down menu.

A new context can be created through the main page or the following link.

https://dtz.rocks/new/ | Nuevo contexto

In Terraform, the context is implicitly derived from the user session or fetched using the dtz_context data source—even if it’s not explicitly declared in the resource block.

Administrador del contexto

Context admin is a role that allow the owning identity the right to control rights and roles regarding the context. The creator of the context always gets assigned the role of context admin.

Also a new identity is created for the context, which serves as service principle within the context. The identity is created with the following alias.

admin@{context_id}.dtz.rocks

All Context admins automatically get access to all used services within the context.