We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
|
values.yml
Hey there,
this is similar to #118.
I have following in a 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
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey there,
this is similar to #118.
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:
The text was updated successfully, but these errors were encountered: