pegasystems
Specifying additonal web.xml snippet
Is your feature request related to a problem? Please describe.
To configure a JMS Listener, we need to add
We need a way to pass in the web.xml updates more easily.
Describe the solution you'd like
For our use case, where we simply need to add a snippet inside the
Describe alternatives you've considered The Helm chart allows for a web.xml to be placed in the deploy/config directory of the chart, but this then means that the chart is specific to a particular application and isn't generic for use with any values.yaml.
The existing custom.webXML capability to pass in the entire file could be more convenient if it supported an external secret. That way, you wouldn't need to embed the 1600 line web.xml in your values.yaml. However if there's any update to the OOTB web.xml in a patch or new minor release we would need to identify the change and update our secret properly. This at best adds additional work to every update, and at worst could lead to use of an incorrect web.xml. For use cases where we're only adding to the web.xml it's preferable to insert a snippet at runtime.
We also considered whether specifying specific changes to context.xml and web.xml makes sense for end users that just want to implement JMS. Currently we need to have some understanding of the internals of Pega's docker image. Maybe there could be a more abstract way to describe JMS resources and references, and the Helm code determines how to turn those elements into changes to the appropriate config files in the runtime image. We don't know if it's feasible to do this in an abstract way and still support all possible JMS integrations.
