You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the management of secrets for devs is entirely ad-hoc. This lends itself to unfortunate incidents where monstrously huge .env files contain all the secrets and linger on filesystems just waiting to be unintentionally posted somewhere public.
We should have a CLI that every developer can access as a standard part of their environment which would either write temporary environment files to be deleted on process exit, or even better just use the process environment manager so they're never written at all.
Plan/Design
The text was updated successfully, but these errors were encountered:
Description/Context
Right now the management of secrets for devs is entirely ad-hoc. This lends itself to unfortunate incidents where monstrously huge .env files contain all the secrets and linger on filesystems just waiting to be unintentionally posted somewhere public.
We should have a CLI that every developer can access as a standard part of their environment which would either write temporary environment files to be deleted on process exit, or even better just use the process environment manager so they're never written at all.
Plan/Design
The text was updated successfully, but these errors were encountered: