Skip to content

Switch to Flux/SOPS for secrets #3175

Description

@sleepycat

The way we're handling secrets is pretty basic, and it's a pain point for deployments.
Certain secrets are just assumed to exist in some cases, and in others we need to create them.
Using SOPS allows us to check the secrets in, treating them consistently across environments and letting the secrets travel/live with the rest of the config.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    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