secrets

Describe the solution you'd like
I'd like to go back to using a CHANGELOG.md to track changes. This will be the first step in updating the ci/cd process to increase the frequency of patches/deploys.

Additional context
Go through https://github.com/zricethezav/gitleaks/releases and create a CHANGELOG.md file

cc @zricethezav

Great tool. What if I want to search for a domain or org name in combination with all the signatures? Is this possible currently?

Hi,
This is a useful tool for any DevOps/SRE teams managing K8S clusters and apps.
One question though, will this be able to detect changes to Secrets stored in an external store like the GoDday one or the HashiCorp Vault.
thanks,
KK

Starting at the "Create a staging environment", the steps described in the guide quickly outpace the explanations and it was not obvious to me what was going on. The quickstart assumes knowledge of concepts (environments, machines) that I would have liked to see brief explanations of.

The Quickstart could also use now.sh as an example deployment environment so that the user can follow along wit

The files on PyPI have these hash values:

• SHA256
• MD5
• BLAKE2-256

If print the hash values, people can easily verify whether the file on PyPI was automatically uploaded by CI script.
It is best to print a pretty-print table.

I am running from a user through which test environment was created on aks.
I followed the steps mentioned in the quick start guide and below is the error I got when I describe the secret CRD.

  Type     Reason         Age                     From                     Message
  ----     ------         ----                    ----                     -------
  Warning  ErrAzureVault  7m12