Remove sensitive .env files and add .env.example templates #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔒 Problem
The repository contains
.envfiles (gateway.env,itest.env,userservice.env) with sensitive information such as OAuth secrets, Redis passwords, and database credentials.🧩 Solution
.envfiles from version control..env.exampletemplates for each service..gitignoreto prevent committing real environment files.The previous secrets still exist in the Git history.
It is recommended to use a tool like
bfg-repo-cleanerto remove them permanently.