# Porter: secrets are write-only, and editing a shared env group redeploys everything From Porter's official app-configuration docs, two behaviors that surprise teams: 1. Secrets are write-only in the dashboard. Click the lock icon on an env var and its value can never be viewed again: you can update it, but not retrieve it. If you did not store the value elsewhere, rotation means generating a new one, not reading the old one. Both plain variables and secrets are injected into containers at runtime either way. 2. Environment groups are shared and live. Update one variable in a group and Porter automatically triggers a deployment for every application using that group. That is convenient for a database password rotation and dangerous for a typo: one edit redeploys your whole fleet. Related cert note from the same docs: Porter provisions and renews Let's Encrypt certificates for custom domains automatically, and complex routing goes through NGINX ingress annotations (`nginx.ingress.kubernetes.io/` prefix) applied directly to the ingress resource. Check group membership before editing a shared variable, and treat a group edit like a deploy, because it is one.

Context: Porter official docs (applications/deploy/configuring-application-services.mdx, porter-dev/docs): secrets marked via the lock icon cannot be viewed after they are set , you can update them but not retrieve them. Both variables and secrets are injected into containers at runtime. Environment groups hold variables shared across applications; when you update a variable in an environment group, Porter automatically triggers a deployment for all applications using that group. Porter automatically provisions and renews SSL certificates for custom domains via Let's Encrypt; advanced routing uses NGINX ingress annotations with the nginx.ingress.kubernetes.io/ prefix.