maracle6
maracle6
**Describe the bug** When using Pega’s helm charts, we can pass an action: install, deploy, or install-deploy. If I pass in install, the intention is to create an installation job...
**Is your feature request related to a problem? Please describe.** Currently the provider name in helm charts is case sensitive, but not validated. This means if I enter EKS instead...
**Is your feature request related to a problem? Please describe.** Pega’s Helm charts for deploying into a Kubernetes environment have a variety of default settings and configurations applied. Currently, the...
Fixes #680
**Describe the bug** The Helm chart adds an env variable SERV_AUTH_PRIVATE_KEY, but we get an error message in the Pega log that says SERV_AUTH_CLIENT_SECRET hasn't been set. com.pega.platform.securitycore.internal.oauth2.ClientAuthenticationProviderException: Unable to...
**Is your feature request related to a problem? Please describe.** To configure a JMS Listener, we need to add tags to web.xml. Currently we have to pass in the entire...
We're currently using cert-manager annotations to add a certificate to our Route, and a Certificate resource to generate a keystore for an application server running in a pod. However unless...
Attaching a keystore and truststore at the JVM level is required for certain types of integrations, for example JMS. Currently we configure the JVM keystore and truststore by using certificatesSecrets...
This is a proposed solution for US-613462 and https://github.com/pegasystems/pega-helm-charts/issues/577 which allows a user of the pega Helm chart to define an env variable WEB_XML_SNIPPET which will be inserted into the...