Skip to content

Drop secrets from Git #57

@poludnev

Description

@poludnev

To drop secrets from Git as a developer, follow these steps:

  • Identify any secrets or sensitive information that have been committed to your Git repository. This could include things like API keys, passwords, or access tokens.
  • Remove the secrets from the Git repository by using git filter-branch or git rm commands. This will rewrite the repository's history to remove any instances of the secret.
  • Change the storage token before deploying the application to ensure that it is not vulnerable to any potential attacks.
  • Update the deploy manual to include a section on the new storage token. This could include instructions on how to generate a new token, where to store it, and how to use it in the deployment process.
  • Finally, add a brief note in the README.md file to remind other developers to never commit sensitive information to the Git repository. You could include a few lines about best practices for handling secrets, such as using environment variables or secure storage services.

By following these steps, you can help ensure that your application's sensitive information remains protected and secure.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

Status

Ideas

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions