Overview

To enable our Helm users to leverage support for initializing groups as part of application start-up we need to extend the existing orchestration.security.initialization key to include groups.

Within the Orchestration cluster I am able to use the configuration listed below to configure a number of groups during application startup.

camunda:
  security:
    initialization:
	groups:
          - group-id: <String>
             name: <String>
             description: <String>
             users:
               - <String> //example ben.sheppard@camunda.com
                  ...
              clients:
                - <String> //example modeler-client
                  ...
              mapping-rules:
                - <String> // identity-mapping-rule
                  ...
              roles:
                - <String> // developer
                  ...
           ... 

ACs

• I can configure a set of groups for the Orchestration cluster that are created during startup

Tests

• Given that I configure an group, when install the helm charts, the orchestration component starts with the configured group