Skip to content

Add Keeper as a supported Backend #476

@ghost

Description

Describe the solution you'd like
Keeper is a pretty popular secret manager that might be a good candidate to add as a supported backend.

What is the added value?
Any organization who uses Keeper would be able to retain it as the single source of truth for secrets and not need to use another backend.

Give us examples of the outcome

Provide templates if you are proposing changes in the CRD. Provide example workflows or code snippets if they make sense to present.

Observations (Constraints, Context, etc):

Keeper has some documentation on interacting with a vault via Go already here. I'm mostly submitting this issue as a way to gauge community support for Keeper as a backend. If I made it and submitted a pull request, would anyone use it? What kind of features are you all interested in?

Metadata

Metadata

Assignees

No one assigned

    Labels

    StaleThis issue/Pull Request is stale and will be automatically closed

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions