# 03-Jun-2026 — self-heal missing NODE_ENV when resuming an environment [ref: #260](https://github.com/nbarrett/ngx-ramblers/issues/260)

## [build 665](https://github.com/nbarrett/ngx-ramblers/actions/runs/26873625529) — [commit 22bb46e](https://github.com/nbarrett/ngx-ramblers/commit/22bb46e10d9c1bc096f69c9d8d041e0c6e7d415f)

_____

#260 made resumeEnvironment self-healing for AUTH_SECRET but classified
every other missing REQUIRED_SECRET as unrecoverable. NODE_ENV was added to
REQUIRED_SECRETS and so fell into that bucket alongside AWS_* and MONGODB_URI,
aborting any resume with "missing required secrets [NODE_ENV] that cannot be
auto-generated" - despite NODE_ENV having a known constant value ("production",
the same value the create wizard hardcodes at environment-setup-service.ts:145).

Add a STATIC_SECRET_DEFAULTS registry for required secrets that have a fixed
default rather than a generated one. NODE_ENV now self-heals to "production"
and is persisted to the environment record, while AUTH_SECRET keeps its random
generator and AWS_*/MONGODB_URI stay unrecoverable. Any future constant-valued
required secret just needs one line in the registry.