environment-secrets

To securely manage environment variables and secrets, you can view, set, and delete configuration data while scoping variables across shared, development, and production environments to isolate deployment configurations safely.

The safest way to request API keys and credentials is to use an explicit request mechanism rather than storing secrets directly. This enforces safe handling by requiring users to grant access at runtime with environment scoping and validation.

Yes, you can scope feature flags and deployment configuration separately. The environment scoping mechanism supports shared, development, and production scopes, ensuring variables are validated and isolated per deployment target.

You can view and delete existing environment variables using the dedicated view and delete commands. This allows you to inspect current configurations and remove outdated or unnecessary environment variables across your deployment scopes.

You should use an explicit request workflow to prevent direct secret storage, which reduces exposure risks. By requesting secrets at runtime with validation, you enforce safe handling and avoid persisting sensitive credentials in your environment.