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.
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: