PEC-REP/Current/GIMPEGuide/ConfigureGSP - Revision history

WikiSysop at 13:31, March 10, 2023

2023-03-10T13:31:34Z

WikiSysop at 16:46, September 29, 2022

2022-09-29T16:46:52Z

Show changes

WikiSysop at 14:31, September 29, 2022

2022-09-29T14:31:25Z

WikiSysop at 19:46, September 28, 2022

2022-09-28T19:46:15Z

Show changes

WikiSysop at 19:31, September 28, 2022

2022-09-28T19:31:15Z

Show changes

WikiSysop at 16:46, September 2, 2022

2022-09-02T16:46:14Z

Show changes

WikiSysop at 16:16, September 2, 2022

2022-09-02T16:16:14Z

Show changes

WikiSysop at 06:31, August 12, 2022

2022-08-12T06:31:59Z

Show changes

WikiSysop at 13:30, April 20, 2022

2022-04-20T13:30:30Z

WikiSysop at 19:53, March 30, 2022

2022-03-30T19:53:11Z

Show changes

@@ Line 50: / Line 50: @@
 Genesys Info Mart, GIM Stream Processor, and GIM Configuration Adaptor helm charts all support advanced templating that allow the helm to create the pull secret automatically; hence the variation in syntax.
 |Status=No
-}}
+}}{{Section
 |sectionHeading=Kafka
 |anchor=GSP_Kafka_Configuration
@@ Line 116: / Line 115: @@
 </source>
 '''Note:''' The <code>host</code> parameter is ignored.
 ====GKE example====
@@ Line 158: / Line 135: @@
        secretKey: "<secret key>"
        pathStyleAccess: "true"
 </source>
 |Status=No
@@ Line 228: / Line 180: @@
 {{AnchorDiv|GSP_Config_ArbitraryUIDs}}
 |Status=No
 }}{{Section

@@ Line 16: / Line 16: @@
 To enable S3-compatible storage to store data that GSP requires during processing, see [[{{FULLPAGENAME}}#Storage|Configure S3-compatible storage]], below.
-You can also specify values in the '''values.yaml''' file to override the default values of configuration options that control GSP behavior and to customize user data and Outbound field mappings. <!--{{Editgrn_open}}<font color=red>'''Writer's note:''' Uncomment the link after the referenced section is published.</font> For more information, see [[{{FULLPAGENAME}}#Options|Configure GSP behavior]].{{Editgrn_close}}-->
+You can also specify values in the '''values.yaml''' file to override the default values of configuration options that control GSP behavior and to customize user data and Outbound field mappings.
 At a minimum, you must override the following key entries in the GSP '''values.yaml''' file:
@@ Line 24: / Line 24: @@
 *:<tt>tag</tt> — ''the container image version''
 *<tt>imagePullSecrets:</tt>
-*:<tt>pureengage-docker-dev</tt> or <tt>pureengage-docker-staging</tt> — ''the secret from which Kubernetes will get credentials to pull the image from the registry''<!--{{Editgrn_open}}<font color=red>'''Writer's note:''' The PAT team instructions show jfrog-stage-credentials but that parameter is not in the values.yaml?</font>{{Editgrn_close}}-->
+*:<tt>pureengage-docker-dev</tt> or <tt>pureengage-docker-staging</tt> — ''the secret from which Kubernetes will get credentials to pull the image from the registry''<!--<font color=red>'''Writer's note:''' The PAT team instructions show jfrog-stage-credentials but that parameter is not in the values.yaml?</font>-->
 *<tt>kafka:</tt>
 *:<tt>bootstrap</tt> — ''the Kafka address to align with the infrastructure Kafka''
-<!--{{Editgrn_open}}<font color=red>'''Writer's note:''' Should we add a note that the storage:pvc parameter is not used?</font>{{Editgrn_close}}-->
+<!--<font color=red>'''Writer's note:''' Should we add a note that the storage:pvc parameter is not used?</font>-->
 If topic names in your Kafka configuration have been customized, you must also modify the <tt>kafka:topic</tt> parameter values to match. For more details about the required Kafka topics, see {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=PlanningGSP|anchor=Kafka|display text=Kafka configuration}}.
@@ Line 156: / Line 156: @@
 |anchor=Options
 |alignment=Vertical
-|structuredtext=You can specify values in the '''values.yaml''' file to override the default values of configuration options that control GSP behavior and to customize user data and Outbound field mappings. For more information, see [[{{FULLPAGENAME}}#Options|Configure GSP behavior]].
+|structuredtext=You can specify values in the '''values.yaml''' file to override the default values of configuration options that control GSP behavior and to customize user data and Outbound field mappings.
 You can override aspects of the default configuration to modify GSP behavior and customize the way data is stored in the Info Mart database.
@@ Line 166: / Line 166: @@
 *[[{{FULLPAGENAME}}#Outbound|Outbound record field mappings]], to map custom CX Contact record field data to Outbound-related tables and columns in the Info Mart database
 -->
 {{AnchorDiv|ConfigOptions}}
 ===Customize configuration option settings===

@@ Line 49: / Line 49: @@
 ===Config Maps===
 Helm creates a number of Config Maps based on option values you specify in the '''values.yaml''' file<!-- (see [[{{FULLPAGENAME}}#Options|Configure GSP behavior]])-->. There are no Config Maps you can configure directly.
 |Status=No
 }}{{Section