environment-secrets

To safely manage environment variables and secrets for deployment, you can view existing configurations across shared, development, and production scopes, update non-sensitive variables, delete obsolete keys, and request missing secrets without exposing sensitive values.

You cannot view existing API keys or credentials directly, as the system prevents reading secret values to ensure runtime safety. You can only check whether required secrets exist across your environment scopes before requesting missing values.

The best way to request missing secrets is to pause execution and use the secure acquisition mechanism to collect required credential values directly from users, ensuring sensitive data is never set or exposed directly in the configuration.

You cannot update runtime-managed environment variables, as the system explicitly prevents modification of these keys. You can only update non-sensitive environment variables and remove outdated configuration keys from the appropriate scope.

You need to rotate credentials and clean up deprecated configuration during deployment readiness checks, onboarding new environments, or troubleshooting missing API keys to prevent conflicts caused by obsolete variables.