Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra env vars cause helm to crash #581

Closed
callumforrester opened this issue Aug 2, 2024 · 1 comment · Fixed by #582
Closed

Extra env vars cause helm to crash #581

callumforrester opened this issue Aug 2, 2024 · 1 comment · Fixed by #582
Labels
bug Something isn't working

Comments

@callumforrester
Copy link
Contributor

The extraEnvVars field in the helm chart causes helm to panic when not empty, for example

extraEnvVars: |
 - name: BEAMLINE
   value: i04

leads to

install.go:222: [debug] Original chart version: ""
install.go:239: [debug] CHART PATH: /home/vid18871/projects/bluesky/blueapi/helm/blueapi


Error: template: blueapi/templates/deployment.yaml:97:27: executing "blueapi/templates/deployment.yaml" at <.Values.extraEnvVars>: can't evaluate field Values in type string
helm.go:84: [debug] template: blueapi/templates/deployment.yaml:97:27: executing "blueapi/templates/deployment.yaml" at <.Values.extraEnvVars>: can't evaluate field Values in type string
@callumforrester callumforrester added the bug Something isn't working label Aug 2, 2024
@callumforrester
Copy link
Contributor Author

Appears to be caused by the with .Values.extraEnvVars that was added in #520

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant