secret

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?

I was testing the site creation flow on Android landscape.

When you get to the last step 'Site created':

• the preview is on the left
• the title and action is on the right
• however the title and action are centred to the preview, and get cut off screen
• I think they are probably meant to be centred to the screen, rather than the preview, so that they appear next to the preview above the

Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

Is your feature request related to a problem? Please describe.
Whenever I update one of my dependencies in a bazel workspace, I often have to reset the SHA for one of my [package-type].bzl files since these also contain SHA hashes that are not sensitive and talisman interprets as secrets.

Describe the solution you'd like
The 'node' scope fixed a similar problem I had with the package-

We want to add documents that run secretlint only on changed files on Pull Request.

name: Secretlint
on: [pull_request]

# secretlint + git diff on Pull Request
# https://github.com/secretlint/secretlint

jobs:
  test:
    name: "Secretlint"
    runs-on: ubuntu-18.04
    steps:
      - name: checkout
        uses: actions/checkout@v2
      - uses: technote-space/get-diff-a

It seems that a common way of storing non-Unicode secrets in Vault is to base64-encode them. Is there currently a way to mount these through the CSI provider without adding a manual decoding process?
If not, the Azure driver supports an objectEncoding property (see Azure/secrets-store-csi-driver-provider-azure#236). Would you accept a PR that adds a similar feature?