environment-secrets

Managing environment variables across scopes involves viewing existing settings, updating non-sensitive values, and deleting outdated keys for shared, development, or production scopes. Sensitive secrets are requested from the user instead of being hardcoded.

Requesting missing secrets during deployment setup is handled by prompting the user for sensitive values at runtime. This prevents hardcoding secrets and ensures configuration is safely provided without exposing sensitive data in the environment variables.

Updating non-sensitive environment variables is supported while preventing modification of runtime-managed variables. You can safely add or update configuration for shared, development, and production scopes without breaking active runtime configuration.

Cleaning up obsolete environment variables during a configuration migration requires deleting outdated keys to prevent stale configuration and conflicts. Discover existing settings first, then remove obsolete keys before applying new environment scoping.

Avoiding hardcoded secrets in environment variables prevents sensitive values from being exposed in configuration files. Requesting secret values from the user at runtime ensures sensitive data remains separate from non-sensitive environment settings.

Environment variable management works for runtime troubleshooting by discovering existing settings across shared, development, and production scopes. You can inventory configuration and identify missing or outdated keys causing runtime issues.