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
With the current way of setting helm values via command line we have 2 issues:
If the deploy script references an env variable, it may be difficult to not overwrite the value and use the default from values.yaml
Passing a cron like schedule is difficult because of globbing.
Possible Solutions:
Use a lot of shell if statements (does not solve Problem 1)
Use a more powerful templating method:
The deployment github actions just set the env variables they want to set, and then we template a second values file and deploy with that
values template (here php, we could use any other template engine)
With the current way of setting helm values via command line we have 2 issues:
Possible Solutions:
Use a lot of shell if statements (does not solve Problem 1)
Use a more powerful templating method:
values template (here php, we could use any other template engine)
And then in the action:
The text was updated successfully, but these errors were encountered: