Add secret vault support for the gateway controller
Open
@nimsara66 is already working on this.
Since Dec 19, 2025.
Area/AIGateway
Area/Gateway
Type/Task
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
In the current gateway implementation, there is no support for managing secrets. For example, when creating an LLM provider, the upstream authentication API key must be provided in plain text. The requirement is to support a $secret{ref} syntax in the provider.yaml, which can be resolved at runtime by the gateway controller. Additionally, there should be a mechanism to perform CRUD operations on these secrets, exposed through the gateway controller’s REST API.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.