environment-secrets

To securely manage environment variables and secrets, you can view, set, and delete values across shared, development, and production environments using centralized controls that prevent direct storage of sensitive secrets and enforce safe workflows.

No, you cannot store sensitive secrets directly in environment variables. The system prevents direct storage of secrets to reduce exposure and instead uses guided prompts to request secrets from users safely.

The best way to request secrets is by using guided prompts that validate usage and prevent the direct storage of sensitive values, ensuring secrets are safely handled across shared, development, and production environments.

You cannot modify certain runtime-managed environment variables because the system validates usage and prevents their modification to avoid misconfigurations and ensure safe DevOps workflows.

To clean up obsolete environment variables in your DevOps workflow, you can delete them using centralized controls that validate usage and help reduce misconfigurations across your shared, development, and production environments.