Closed BWibo closed 1 year ago
Hey there,
I have following in a values.yml:
values.yml
readinessProbe: # -- Enable/disable readiness probe # [Readiness probe](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes) # See the [API reference](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#Probe) for details. # Use `readinessProbe.probe: {}` to configure # [readinessProbe probe](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) enabled: true initialDelaySeconds: 10 periodSeconds: 5 timeoutSeconds: 1 successThreshold: 1 failureThreshold: 5 terminationGracePeriodSeconds: probe: exec: command: [ bash, -c, 'wget -S "http://127.0.0.1:3000/api/health" |& grep "200 OK"' ]
Apparently, the pipe in the command is interpreted as a column separator in the generated markdown:
| readinessProbe.probe.exec.command[2] | string | `"wget -S \"http://127.0.0.1:3000/api/health\" |& grep \"200 OK\""` | |
Rendered result:
Escaping the pipe manually seems to help:
| readinessProbe.probe.exec.command[2] | string | `"wget -S \"http://127.0.0.1:3000/api/health\" \|& grep \"200 OK\""` | |
Version info:
$ docker run --rm --volume "$PWD/helm/charts:/helm-docs" -u $(id -u) jnorwood/helm-docs:latest --version helm-docs version 1.11.0
Sorry, wrong repo.
Hey there,
I have following in a
values.yml
:Apparently, the pipe in the command is interpreted as a column separator in the generated markdown:
Rendered result:
Escaping the pipe manually seems to help:
Version info: