DES/Current/DESPEGuide/Configure - Revision history

WikiSysop at 07:30, July 13, 2023

2023-07-13T07:30:37Z

WikiSysop at 15:30, December 5, 2022

2022-12-05T15:30:36Z

WikiSysop at 10:15, July 25, 2022

2022-07-25T10:15:39Z

Show changes

WikiSysop at 07:45, April 1, 2022

2022-04-01T07:45:27Z

Show changes

Marudhu.pandian@genesys.com: Published

2021-11-24T07:21:09Z

Published

Marudhu.pandian@genesys.com: Published

2021-11-23T08:38:54Z

Published

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:28:45Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Marudhu.pandian@genesys.com: Published

2021-10-27T20:00:54Z

Published

Ed.jamer@genesys.com at 18:35, October 9, 2021

2021-10-09T18:35:33Z

Marudhu.pandian@genesys.com: Published

2021-10-04T08:13:53Z

Published

@@ Line 841: / Line 841: @@
 {{!}}-
 {{!}}<code>das.dasSecrets.secrets</code>
-{{!}}Key and value pairs containing the secrets, such as a username and password.
+{{!}}Key value pairs containing the secret, such as, username and password.
 {{!}}Optional
 {{!}}
@@ Line 1,259: / Line 1,259: @@
 {{!}}-
 {{!}}<code>das.dasConfig.envs.DAS_SERVICES_ELASTICSEARCH_HOST</code>
-{{!}}Elasticsearch server host name with http:// prefix. For example, [http://es-service/ http://es-service]. The input should be a string, within double quotes.
+{{!}}Elasticsearch server host name with an http:// prefix. For example, [http://es-service/ http://es-service]. The input should be a string within double quotes.
 {{!}}Optional
 {{!}}" "
@@ Line 1,265: / Line 1,265: @@
 {{!}}<code>das.dasConfig.envs.DAS_SERVICES_ELASTICSEARCH_PORT</code>
 {{!}}Elasticsearch port. For example, <code>"80"</code>. The input should be a string, within double quotes.
 {{!}}Optional
 {{!}}" "

@@ Line 232: / Line 232: @@
 {{!}}-
 {{!}}<code>designer.volumes.logsPvc.pvName</code>
-{{!}}	The PV's name to which the PVC must be bound (applicable only when <code>designer.volumes.logsPvc.type</code> is static).
+{{!}}The PV's name to which the PVC must be bound (applicable only when <code>designer.volumes.logsPvc.type</code> is static).
 {{!}}
 {{!}}
@@ Line 2,042: / Line 2,042: @@
 {{!}}Yes
 {{!}}When enabled, Dialogflow CX bot type is added to the bot registry and available for selection in the '''Bot provider''' drop-down when you configure a new bot.
 {{!}}<code>false</code>
 {{!}}}

@@ Line 11: / Line 11: @@
 |structuredtext=The following sections provide information on the various settings that have to be configured in Designer and DAS. The configuration settings listed below will be used during the deployment of Designer and DAS. That is, these settings will be used during initial deployment/upgrade. These settings can be configured in the '''values.yaml''' Helm file.
-For more information about how to override Helm chart values, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=HelmOverrides}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide.{{NoteFormat|Depending on the cloud platform or the container orchestration platform that you are deploying Designer on, you might have to carry out some additional steps specific to that platform. For more information, navigate to the required topic in the '''Cloud platform specific information''' section on the {{Link-SomewhereInThisVersion|manual=DESPEGuide|display text=About}} page.|}}
+For more information about how to override Helm chart values, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=HelmOverrides}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide.{{NoteFormat|Depending on the Kubernetes platform or the container orchestration platform that you are deploying Designer on, you might have to carry out some additional steps specific to that platform. For more information, navigate to the required topic in the '''Kubernetes platform specific information''' section on the {{Link-SomewhereInThisVersion|manual=DESPEGuide|display text=About}} page.|}}
 ==Designer deployment settings==
@@ Line 395: / Line 395: @@
 {{!}}
 {{!}}Optional
-{{!}}<code>{{instance}}</code>
+{{!}}<code>&#10100;&#10100;instance&#10101;&#10101;</code>
 {{!}}-
 {{!}}<code>designer.prometheus.serviceMonitor.enabled</code>
@@ Line 820: / Line 820: @@
 {{!}}-
 {{!}}<code>das.volumes.podPvc.create</code>
-{{!}}This volume is usually created to mount a local disk onto DAS for syncing data in case cloud storage is used for storing Designer files. This value has to be <code>true</code> or <code>false</code> depending on whether the local disk is needed or not
+{{!}}This volume is usually created to mount a local disk to a  DAS container for syncing data in case cloud storage is used for storing Designer files. This value has to be <code>true</code> or <code>false</code> depending on whether the local disk is needed or not
 {{!}}Optional
 {{!}}<code>false</code>
@@ Line 975: / Line 975: @@
 {{!}}Hostnames to be configured in ingress for the DAS service.
 {{!}}Mandatory if ingress is enabled.
-{{!}}- <app1>.example.com
+{{!}}- <app1 > .example.com
 {{!}}-
 {{!}}<code>das.ingress.tls</code>
@@ Line 1,100: / Line 1,100: @@
 {{!}}
 {{!}}Optional
-{{!}}<code>{{pod}}</code>
+{{!}}<code>&#10100;&#10100;pod&#10101;&#10101;</code>
 {{!}}-
 {{!}}<code>das.prometheus.instance</code>
 {{!}}
 {{!}}Optional
-{{!}}<code>{{instance}}</code>
+{{!}}<code>&#10100;&#10100;instance&#10101;&#10101;</code>
 {{!}}-
 {{!}}<code>das.prometheus.serviceMonitor.enabled</code>

@@ Line 11: / Line 11: @@
 |structuredtext=The following sections provide information on the various settings that have to be configured in Designer and DAS. The configuration settings listed below will be used during the deployment of Designer and DAS. That is, these settings will be used during initial deployment/upgrade. These settings can be configured in the '''values.yaml''' Helm file.
-For more information about how to override Helm chart values, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=HelmOverrides}} in the ''Setting up Genesys Engage Cloud Private Edition'' guide.{{NoteFormat|Depending on the cloud platform or the container orchestration platform that you are deploying Designer on, you might have to carry out some additional steps specific to that platform. For more information, navigate to the required topic in the '''Cloud platform specific information''' section on the {{Link-SomewhereInThisVersion|manual=DESPEGuide|display text=About}} page.|}}
+For more information about how to override Helm chart values, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=HelmOverrides}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide.{{NoteFormat|Depending on the cloud platform or the container orchestration platform that you are deploying Designer on, you might have to carry out some additional steps specific to that platform. For more information, navigate to the required topic in the '''Cloud platform specific information''' section on the {{Link-SomewhereInThisVersion|manual=DESPEGuide|display text=About}} page.|}}
 ==Designer deployment settings==

@@ Line 1,325: / Line 1,325: @@
 {{!}}-
 {{!}}Setting Name
-{{!}}lowsettings.json
+{{!}}flowsettings.json
 {{!}}tenantsettings.json
 {{!}}DesignerEnv
@@ Line 1,919: / Line 1,919: @@
 {{!}}Default Value
 {{!}}-
-{{!}} rowspan="2"{{!}}Audio
+{{!}} rowspan="3"{{!}}Audio
 {{!}}<code>enableBulkAudioImport</code>
 {{!}}Optional
@@ Line 1,932: / Line 1,932: @@
 {{!}}yes
 {{!}}If this feature is enabled, Designer will validate invalid grammar files during grammar upload and you can upload only valid grammar files (GRXML or Nuance compiled binary grammar files).
 {{!}}<code>false</code>
 {{!}}-
@@ Line 1,972: / Line 1,979: @@
 {{!}}Yes
 {{!}}Enable reporting each Shared Module call as an internal milestone. If disabled, Shared Module calls will not generate a milestone.
 {{!}}<code>false</code>
 {{!}}}

@@ Line 10: / Line 10: @@
 |alignment=Vertical
 |structuredtext=The following sections provide information on the various settings that have to be configured in Designer and DAS. The configuration settings listed below will be used during the deployment of Designer and DAS. That is, these settings will be used during initial deployment/upgrade. These settings can be configured in the '''values.yaml''' Helm file.
 ==Designer deployment settings==
@@ Line 293: / Line 295: @@
 {{!}}-
 {{!}}<code>designer.securityContext.runAsUser</code>
-{{!}}This setting controls which user ID the containers are run with. This can be configured to run Designer as a non-root user. Currently, only a '''Genesys''' user is supported by the Designer base image. <code>500</code> is the ID of the Genesys user and cannot be modified.<br>
+{{!}}This setting controls which user ID the containers are run with. This can be configured to run Designer as a non-root user. You can either use the '''Genesys''' user or arbitrary UIDs. Both are supported by the Designer base image. <code>500</code> is the ID of the Genesys user.<br>
 The file system must reside within the Genesys user account in order to run Designer as a Genesys user. Change the NFS server host path to the Genesys user:
 <code>chown -R genesys:genesys</code>.
@@ Line 300: / Line 302: @@
 {{!}}-
 {{!}}<code>designer.securityContext.runAsGroup</code>
-{{!}}Controls which primary group ID the containers are run with. This can be configured to run Designer as a non-root user. Currently, only a '''Genesys''' userGroup (GID - <code>500</code>) is supported by the Designer base image.
+{{!}}Controls which primary group ID the containers are run with. This can be configured to run Designer as a non-root user. You can either use the  '''Genesys''' userGroup (GID - <code>500</code>) or arbitrary GIDs. Both are supported by the Designer base image.
 {{!}}Optional
 {{!}}
@@ Line 962: / Line 964: @@
 {{!}}-
 {{!}}<code>das.securityContext.runAsUser</code>
-{{!}}This setting controls which user ID the containers are run with and can be configured to run DAS as a non-root user. Currently, only a '''Genesys''' user is supported by the DAS base image. <code>500</code> is the ID of the Genesys user and cannot be modified.
+{{!}}This setting controls which user ID the containers are run with and can be configured to run DAS as a non-root user. You can either use the '''Genesys''' user or arbitrary UIDs. Both are supported by the DAS base image. <code>500</code> is the ID of the Genesys user.
 For more information refer to the [https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ Security Context] topic in the Kubernetes documentation site.
 {{!}}Optional
@@ Line 968: / Line 970: @@
 {{!}}-
 {{!}}<code>das.securityContext.runAsGroup</code>
-{{!}}This setting controls which primary group ID the containers are run with and can be configured to run DAS as a non-root user. Currently, only a '''Genesys''' user group (GID - 500) is supported by the DAS base image.
+{{!}}This setting controls which primary group ID the containers are run with and can be configured to run DAS as a non-root user. You can either use the  '''Genesys''' userGroup (GID - <code>500</code>) or arbitrary GIDs. Both are supported by the DAS base image.
 {{!}}Optional
 {{!}}