2023-07-18 - New Partner config table in Spanner¶
Problem¶
Until now all tenancy level config in spanner was squashed into the tenancy table. This pattern wasn’t workable once we wanted to produce customer level reporting (because a customer may have multiple separate projects)
Solution¶
Create a new spanner table ‘partner’ which holds the high level partner attributes (previously known as domain attributes), these are propagated down when a tenancy is deployed for a partner (allowing customisation at the tenancy level if required). ‘tenancy’ is extended to include two new attributes ‘partner’ and ‘customer’ for grouping/reporting purposes.
Leverage the Magic¶
Leverage the power and simplicty of spanner to re-jig our config structure and seamlessly introduce a new config table and move attributes across from the legacy table, then simply update the /api/tenancy endpoint to combine the data from the different tables.
At the same timw deploy new /api/partner endpoints to allow the viewing and updating of partner level attributes
Magician Partner¶
Until now all tenancy level config in spanner was squashed into the tenancy table. This pattern wasn’t workable once we introduced custom attributes for a partner.
Create a new spanner table ‘partner’ which holds the high level partner attributes (previously known as domain attributes), these are propagated down when a tenancy is deployed for a partner (allowing customisation at the tenancy level if required). ‘tenancy’ is extended to include two new attributes ‘partner’ and ‘customer’ for grouping/reporting purposes.
Last Refreshed¶
Doc Refreshed: 2024-03-02