Andrew Stangl
Andrew Stangl
Similar to this use case, it would be useful to be able to exclude rulesets from the different ones being checked .. we're on `1.24.x`, looking to upgrade to `1.25.x`,...
> You can use file `.chezmoi.yaml.tmpl` (see docs) with this line: `sourceDir: {{ .chezmoi.config.sourceDir | quote }}` It's quite surprising to me to have to do this - I would...
Ah, there is indeed mention of it at: https://www.chezmoi.io/user-guide/setup/#create-a-config-file-on-a-new-machine-automatically It is still surprising that a minimal customised setup isn't possible without the config file template, and just by setting `--source`...
I'm interested in this as well ☺️
+1 - Would be good to add metadata generation as well :)
I've just hit this as well, would love to have it merged 🙏
I'm experiencing the same thing - wrong model detected. Same as the OP, I have an `IO series 5`, but it's being detected as `Smart Series 7000`
> @thinkbiggerltd Think you need to add `imagePullSecrets` to your spec > > ```yaml > template: > spec: > imagePullSecrets: > - name: your-secret-name > containers: > - name: runner...
An update: even though runner pods themselves are coming up with the `imagePullSecrets` applied, when I set `container.image` in a workflow, the resulting pod doesn't have `imagePullSecrets` set
We're experiencing this as well - it seems any `KUBECONFIG` related environment variables are being ignored, and the internal K8s environment variables are being used instead