Skip to content

Document/enforce best-practices for config secrets as environment vars via .env #75

@cacama-valvata

Description

@cacama-valvata

disallow the user to put creds into bcds.yaml, forcing env vars. if they want to put it into a file, it must be .env.

i think having init cmd adding a .gitignore that lists .env is not a bad idea also

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