I have spent a good amount of time lately looking into the GoDaddy open-source CRD called ExternalSecrets. It's been pretty good to work with, it keeps the actual secret material in AWS Secrets Manager, and polls for changes. When a change is detected it creates/updates a Secret in your Kubernetes cluster. The only issue I've encountered is that you are ...
There are a lot of great open source tools out there for storing secrets in Git. It can be hard to determine the right one for you and your organization—it depends on your use cases and requirements. To help you compare and choose, we'll look at four of the most popular open source tools for secrets management and see how they stack up against each other:
I personally am a fan of Mozilla SOps, we've introduced it to two teams and it's gone down well both times, it has proven easy to implement both with local development and our CI/CD pipelines.
It has support for PGP/GPG to encrypt secrets but also supports Amazon KMS, GCP KMS and Azure KeyVault thus works well in an enterprise cloud-native infrastructure.
Using Git-crypt you can Encrypt (protect) your git repositories,
git-crypt enables transparent encryption and decryption of files in a git repository.
Files which you choose to protect are encrypted when committed, and decrypted when checked out. git-crypt lets you freely share a repository containing a mix of public and private content. git-crypt ...
You can achieve this using Git and Jenkins job. Create a Jenkins Job to deploy your code to server and Setup Git webhook to Call Jenkins job.
Check this link: https://www.serverkaka.com/2019/02/configure-github-webhook-in-jenkins-job-pipeline.html
Create an empty Git repo on the server
Write a Git Hook to deploy the code
Deploy from the local ...