Skip to content

[Feature request]: eyaml is always Sensitive #379

@jcpunk

Description

@jcpunk

Use Case

Currently eyaml keys are decrypted and rendered "as is". This can lead to unintentional disclosure of the content.

Describe the solution you would like

When decrypting, values are automatically cast as Sensitive.

Describe alternatives you've considered

No response

Additional context

If a value was important enough to store encrypted, it seems like Sensitive is a safe expectation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions