Skip to content

Extracting secrets from configs during gitops #376

@zepatrik

Description

@zepatrik

Preflight checklist

Ory Network Project

No response

Describe your problem

When getting the full config, it includes secrets and other keys that might not be exposed in a repository directly.

Similarly, the secrets have to be transmitted for updates nested in the config.

Describe your ideal solution

A CLI flag to redact certain keys on get project, and a flag to set keys on update project.

Workarounds or alternatives

Use the surrounding shell for scripting, e.g.

ory get project --format json | jq '.my.secret.a = "<redacted>" | .other.list_of.[].secrets = "<redacted>"' > output.json

jq ".my.secret.a = $SECRET_FROM_ENV" input.json | ory update project --file -

Version

v1.0.0

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    featNew feature or request.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions