The secrets engine resolves se://<id> references through plugins. Below are candidate backends we're considering, grouped by where they fit in a user's workflow.
Locally-usable backends
Routinely used from a developer's machine, personal/team password managers, or self-hostable secret servers a developer authenticates to with a token.
Cloud-deployment backends
Primarily used by workloads running in a cloud, reading secrets provisioned in that same cloud (IAM role, managed identity, workload identity).
Vote for the plugin you want most scroll down and react with 👍 on the comment for that backend. The more reactions a backend gets, the sooner it moves up our list.
Don't see your secret store? Drop a new comment with the backend you'd like supported and a short note on how you use it (personal workstation, CI, production workloads, …).
The secrets engine resolves
se://<id>references through plugins. Below are candidate backends we're considering, grouped by where they fit in a user's workflow.Locally-usable backends
Routinely used from a developer's machine, personal/team password managers, or self-hostable secret servers a developer authenticates to with a token.
Cloud-deployment backends
Primarily used by workloads running in a cloud, reading secrets provisioned in that same cloud (IAM role, managed identity, workload identity).
Vote for the plugin you want most scroll down and react with 👍 on the comment for that backend. The more reactions a backend gets, the sooner it moves up our list.
Don't see your secret store? Drop a new comment with the backend you'd like supported and a short note on how you use it (personal workstation, CI, production workloads, …).