Skip to content

Remove the SecretStoreSource constructor with optional mutated secret function #304

@stijnmoreels

Description

@stijnmoreels

Is your feature request related to a problem? Please describe.
When designing the secret store, we first had a single option to mutate secret names before secret retrieval. As this grew, we chose to use an options model internally and expose the different options via method overloads, making this constructor obsolete.

Describe the solution you'd like
Remove the SecretStoreSource constructor with a single optional mutated secret function as parameter.

Metadata

Metadata

Assignees

Labels

breaking-changeAll issues that require to do a breaking chnagegood first issueGood for newcomerssecret-storeAll issues related to our secret store

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions