-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Summary: Anemic tenants are supported.
external conditions:
- all outbound data consumed by:
- consumers that only require org_id (e.g. L3 services), or
- consumers using a new API version (where EAN is no longer present), or
- consumers that require EAN and org_id→EAN translation is implemented and anemic tenants are gated
- e.g. receptor gateway, which is going to remain a L0 service but its usage requires Satellite subscription i.e. there is an anemic tenant gate
level characteristics:
- anemic tenants supported
- EAN made optional (nullable) or removed altogether
implementation tasks:
- introduce a new version of interfaces (if applicable)
- remove the EAN column (or make it nullable) in stored data
- remove EAN (or make it optional) in inbound data
- remove EAN (or make it optional) in outbound data
- is blocked by
-
RHCLOUD-18690 [dispatcher] org_id migration to level 3
- Closed
-
RHCLOUD-18886 [playbook-dispatcher] Filter out anemic messages
- Closed
- is related to
-
RHCLOUD-19185 [QE] [Ingress] update Ingress tests to support new L3 API.
- Closed