Guide / Every rule
Secret that no file of the project defines
The check connections/secret-undefined, in the group Connections.
Why it matters
A diagram that names a secret nothing in the project supplies runs with an empty value, and the task fails when the connector reads it. Secrets that only exist in a cloud console or a vault cannot be seen from here, so this is a warning.
How to fix it
Add the secret to connector-secrets.txt, .env, the Compose environment or the Helm values, or correct the name in the diagram.
Where you see it
The Problems tab lists it under Connections, the Connections screen shows it beside the map, and penstock check --only connections reports it as connections/secret-undefined. It also appears in the SARIF and GitHub outputs. This check is free.
Rule details
| Id | connections/secret-undefined |
| Group | Connections |
| Level | Advice: it works, and reads or runs better without it |
Read more: Connections map. All rules: Every rule.