Protecting .env variables
Answered
.dric posted this in #help-forum
.dricOP
Hello!
I'm using Github, and have a developer team.
Is there a way to give them access to use the .env variables without me giving them the variables? Like is there a way to centralize the variables to the repository so anyone who's a collaborator has access, but once they're removed from the repository they dont have access anymore?
This has been an ongoing thought I've been thinking about as I expand my team.
Thanks!
I'm using Github, and have a developer team.
Is there a way to give them access to use the .env variables without me giving them the variables? Like is there a way to centralize the variables to the repository so anyone who's a collaborator has access, but once they're removed from the repository they dont have access anymore?
This has been an ongoing thought I've been thinking about as I expand my team.
Thanks!
Answered by joulev
Not possible. What you can do is to rotate the secrets when someone leaves the team, for example generate a new database connection uri and delete the old connection uri
2 Replies
Not possible. What you can do is to rotate the secrets when someone leaves the team, for example generate a new database connection uri and delete the old connection uri
Answer