Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to optionally set human-readable name to keys in sops config file #366

Open
ajvb opened this issue Jun 29, 2018 · 2 comments
Open

Ability to optionally set human-readable name to keys in sops config file #366

ajvb opened this issue Jun 29, 2018 · 2 comments
Labels
enhancement priority/low Low priority issues

Comments

@ajvb
Copy link
Contributor

ajvb commented Jun 29, 2018

I'd like to be able to set a name for each key in a sops config file. The main benefit for this is the potential to vastly improve error messages on decryption failures when you have a number of PGP keys within the config file. Currently you will have a huge error output and it can be difficult to parse what error is relevant to your key, especially if you don't immediately recognize your fingerprint.
@ajvb ajvb added enhancement priority/low Low priority issues labels Jun 29, 2018
@autrilla
Copy link
Contributor

It'd also be nice to be able to do the same for key groups.

It might also be worth it to support something like:

keys:
- name: user1
  pgp: 1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A
- name: kms-prod
  kms: arn:aws:kms:us-west-2:927034868273:key/fe86dd69-4132-404c-ab86-4269956b4500
groups:
- name: operators
  keys:
  - user1
creation_rules:
- path_regex: \.ops\.yaml$
  key_groups:
  - operators
- path_regex: .*
  key_groups:
  - name: prod
    keys:
    - kms-prod

Although perhaps it's too complex

@autrilla autrilla mentioned this issue Oct 4, 2018
Open
@hobti01
Copy link

hobti01 commented Jun 14, 2019

We put comments in the file which helps:

creation_rules:
  # Operators
  - path_regex: .some-secrets.yaml
    key_groups:
      - pgp:
        # Robot (Deployer)
        - 0367E722878D9586894386ED2E38389A4F9B4FAE
        # Robot (Global Backup)
        - 09EA6D8A1B5E8CE18F3C9FC845E5EF716FB2B767

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement priority/low Low priority issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ajvb @autrilla @hobti01