As a developer, I want to be able to use the helm template engine capabilities to render templates that are not for Kubernetes, such as EAP configuration files, Dockerfiles or any other non-yaml, non-json, non-tpl formatted file that is required as part of the workflow, so that users can benefit from the existing helm templating engine capabilities without requiring learning a new templating language.

As a secondary goal, I want to keep these non kubernetes related templates bundled in the chart, so that everything is bundled in a single location.

The output of this PoC should validate the assertion that we can embed the helm template engine in our CLI to generate these non kubernetes files like helm does for the ones in the templates/ subdirectory, in a similar fashion as the helm command:

$> helm template sample foo