NonexistentTenant

Andromeda answers 404 with the problem type https://uri.etsi.org/ngsi-ld/errors/NonexistentTenant. The tenant the request names doesn't exist. The answer is worded so that a suspended tenant can't be told apart from one that was never created. The specification defines this type and binds it to 404.

When this comes back

• Any read, update, delete or query under a tenant that doesn't exist. Writes are the exception. Six creating operations make the tenant on their first successful write, and a refused write creates nothing. See Tenants.
• The tenant management endpoints, for an unknown tenant. They never list or accept a tenant that doesn't exist.
• A snapshot-scoped request naming a tenant that doesn't exist. Snapshot operations are always local and never create a tenant. See Snapshots.

A request that races the first write to a new tenant can also get this answer, if the broker admits it before that write has stored anything. Given the order the two requests arrived in, that answer is correct.

Example

GET /ngsi-ld/v1/entities/urn:ngsi-ld:Building:1
NGSILD-Tenant: acme-staging

HTTP/1.1 404 Not Found
Content-Type: application/json

{
    "type": "https://uri.etsi.org/ngsi-ld/errors/NonexistentTenant",
    ...
}