-
Notifications
You must be signed in to change notification settings - Fork 152
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
fix-extraEnv-default-value #329
base: master
Are you sure you want to change the base?
Conversation
I messed up the default value for extraEnv. This fixes the jobserver.extraEnv to be an array, which is what the template is expecting.
the tests need to be retried |
@spirosoik / @pfltdv / @stylianosrigas - can you review? |
@pfltdv did you give a try to test locally? |
@spirosoik Yes tested with and without jobserver extra vars. Had no issue at both executions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with merging this.
Would you mind also commenting @ values.yaml
some examples on how the Jobserver extraEnv
directive can be used?
For Example:
https://github.com/mattermost/mattermost-helm/blob/master/charts/mattermost-enterprise-edition/values.yaml#L245-L251
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
@jonathanwiemers - no real reason, other than the 3 week lag on feedback. My need for this was removed as we moved away from mattermost due to the integration and license headaches. |
/update-branch |
Summary
I messed up the default value for extraEnv in #316. This fixes the jobserver.extraEnv to be an array, which is what the template is expecting
Without this change, if trying to use jobserver's extraEnvs, you get this error: