@oraNod Can you please take a look at the values.schema.json and README.md. If you ping me when you're ready, I can provide an env so that you can see the UI and there values in action.
I assume we're going to have to parameterise this so that Infinispan is replaced with $brandname. I would love to pick your brains on how best to go about this.
In order to have the upstream/downstream charts we have to copy the charts to https://github.com/redhat-developer/redhat-helm-charts and perform some packaging. I was thinking that we could create README.md.tpl and values.schema.json.tpl with the required placeholders and generate the actual files from these. We would then have a basic script that can be executed locally to copy the charts with the upstream/downstream values to our local redhat-helm-charts fork in order to create the required PRs.
In this repo README.md and values.schema.json would contain the upstream values.
@oraNod Can you please take a look at the
values.schema.json
andREADME.md
. If you ping me when you're ready, I can provide an env so that you can see the UI and there values in action.I assume we're going to have to parameterise this so that Infinispan is replaced with
$brandname
. I would love to pick your brains on how best to go about this.In order to have the upstream/downstream charts we have to copy the charts to https://github.com/redhat-developer/redhat-helm-charts and perform some packaging. I was thinking that we could create
README.md.tpl
andvalues.schema.json.tpl
with the required placeholders and generate the actual files from these. We would then have a basic script that can be executed locally to copy the charts with the upstream/downstream values to our localredhat-helm-charts
fork in order to create the required PRs.In this repo
README.md
andvalues.schema.json
would contain the upstream values.