[TASK] 8.8 and 8.9 values are updated to include support for tenant initialization #4525
Description
Overview
To enable our Helm users to leverage support for initializing tenants as part of application start-up we need to extend the existing orchestration.security.initialization key to include tenants.
Within the Orchestration cluster I am able to use the configuration listed below to configure a number of tenants during application startup.
camunda:
security:
initialization:
tenants:
- tenant-id: <String>
name: <String>
description: <String>
users:
- <String> //example ben.sheppard@camunda.com
...
clients:
- <String> //example modeler-client
...
mapping-rules:
- <String> // identity-mapping-rule
...
groups:
- <String> // developers
...
roles:
- <String> // software-engineer
...
...
ACs
- I can configure a set of tenants for the Orchestration cluster that are created during startup
Tests
- Given that I configure an tenant, when install the helm charts, the orchestration component starts with the configured tenant