Configure <service_name>
From Genesys Documentation
Revision as of 19:09, June 10, 2021 by Tony.gilchrist@genesys.com (talk | contribs)
This is a draft page; it has not yet been published.
Learn how to configure <service_name>.
Related documentation:
Override Helm chart values
Container environment variables are declared in docker file. Comment above each variable discovers its purpose. Please request a copy of variables fragment if you have no access.
RAA helm chart supplied with default values.yaml. Each helm value supported by gcxi/raa helm chart have description in comments.
You can override values in the Helm charts to configure Private Edition for their deployment environment. For example GIM database connection parameters can be specified in own yaml file as a json line base64 encoded:
raa:
env:
# echo '{"jdbc_url":"jdbc:postgresql://<host>:5432/<gim_database>", "db_username":"<user>", "db_password":"<password>"}' | base64
GCXI_GIM_DB__JSON:|-
eyJqZGJjX3VybCI6ImpkYmM6cG9zdGdyZXNxbDovLzxob3N0Pjo1NDMyLzxnaW1fZGF0YWJhc2U+IiwgImRiX3VzZXJuYW1lIjoiPHVzZXI+IiwgImRiX3Bhc3N3b3JkIjoiPHBhc3N3b3JkPiJ9Cg==
Parameter | Description | Default | Valid values |
---|---|---|---|
service.port | Designer service to be exposed. | 8888 | A valid port. |
... |
Configure Kubernetes
Document the layouts for the following so customers can create them if their Helm chart doesn't include a way to do this:
- ConfigMaps
- Secrets
Configure security
List security-related settings, such as how to set up credentials and certificates for third-party services.