Skip to content

Expose full config via Go API #1682

@nicklasfrahm

Description

@nicklasfrahm

Hi,

I am working on a project where I would like to use SOPS as the secret engine. In this context, I want to be agnostic whether the user is using my CLI or sops to interact with the secret, but that requires that I generate the .sops.yaml in their repository.

Currently, there is no simple public Load function that returns a Config and I am wondering if that is by design. My use-case requires both the full config creation_rules and destination_rules.

I am happy to implement this, but I wanted to know if I am not doing anything wrong here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions