You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently added proxyPass variable does not support templating, which requires hardcoding the value in the values.yaml file or use --set command to set it explicitly as http://<RELEASE_NAME>-rest.
However, it would have been better if the value could be set as template, e.g. http://{{ .Release.Name }}-fst.
Allow proxyPass value to be a template e.g. http://{{ .Release.Name }}-fst.
Use tpl function to render the template while creating the configmap here
Alternatives
Without supporting the templating, end-user always needs to update the values.yaml file or use --set hedera-explorer:.proxyPass=<NEW VALUE> during deployment of their chart with a new release name.
Problem
Recently added proxyPass variable does not support templating, which requires hardcoding the value in the values.yaml file or use
--set
command to set it explicitly ashttp://<RELEASE_NAME>-rest
.However, it would have been better if the value could be set as template, e.g.
http://{{ .Release.Name }}-fst
.Relevant issue: hashgraph/full-stack-testing#410
Solution
proxyPass
value to be a template e.g.http://{{ .Release.Name }}-fst
.tpl
function to render the template while creating the configmap hereAlternatives
Without supporting the templating, end-user always needs to update the
values.yaml
file or use--set hedera-explorer:.proxyPass=<NEW VALUE>
during deployment of their chart with a new release name.Blocks
The text was updated successfully, but these errors were encountered: