ALFMOB-100: Secure sensitive files in the repository #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JoaoPinhoMinder
force-pushed
the
techdebt/ALFMOB-100-secure-sensitive-files-in-the-repository
branch
12 times, most recently
from
78bc918 to
e20f9b0
Compare
JoaoPinhoMinder
requested review from
p4checo,
reisdev and
DanielPrimoMinder
JoaoPinhoMinder
force-pushed
the
techdebt/ALFMOB-100-secure-sensitive-files-in-the-repository
branch
4 times, most recently
from
a5ca7b9 to
1613f56
Compare
JoaoPinhoMinder
force-pushed
the
techdebt/ALFMOB-100-secure-sensitive-files-in-the-repository
branch
9 times, most recently
from
2be837a to
cb7e077
Compare
JoaoPinhoMinder
force-pushed
the
techdebt/ALFMOB-100-secure-sensitive-files-in-the-repository
branch
3 times, most recently
from
b8be0da to
1976752
Compare
JoaoPinhoMinder
force-pushed
the
techdebt/ALFMOB-100-secure-sensitive-files-in-the-repository
branch
3 times, most recently
from
f83298b to
f62ce97
Compare
In order to manage sensitive files, i have: - Set up `git-secret` for encrypting sensitive files in the repository - Created and configured **GPG key pairs** for both the team and CI/CD - Encrypted `GoogleService-Info.plist` files for **Debug and Release**, removing exposed credentials - Added documentation on setting up `git-secret`, importing keys, and managing secrets
JoaoPinhoMinder
force-pushed
the
techdebt/ALFMOB-100-secure-sensitive-files-in-the-repository
branch
from
f62ce97 to
58d577d
Compare
JoaoPinhoMinder
requested review from
p4checo,
reisdev and
DanielPrimoMinder
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket
https://mindera.atlassian.net/browse/ALFMOB-100
Description
In order to manage sensitive files, i have:
git-secretfor encrypting sensitive files in the repositoryGoogleService-Info.plistfiles for Debug and Release, removing exposed credentialsgit-secret, importing keys, and managing secrets