environment-secrets

You can manage environment variables across development and production by viewing, setting, or deleting configuration values and secret keys within shared, development, or production scopes.

It secures secrets by only exposing their presence rather than their values, and prompts users to securely provide any missing secrets or configuration values without hard-coding them into the environment.

You can request missing configuration values by prompting the user to securely provide required secrets, allowing you to verify existing keys and configure environment-specific settings in one workflow.

Yes, you can retrieve a list of current environment variables and secret keys across all scopes, and remove obsolete variables from shared, development, or production deployments as needed.

The best way to add or update non-sensitive environment variables is to set them directly within the desired development, production, or shared scope, ensuring secure handling of configuration values.

You need a dedicated workflow when deploying new services that require verifying required secrets exist, securely providing missing ones, and configuring environment-specific settings without exposing sensitive values.