Repository navigation
⚡️ Feature: Secrets managers support with abstract interface (Infisical, Doppler, etc) #4036
Replies: 7 comments 15 replies
|
I'd also suggest OpenBao as one of the potential supported options. As it is fully open source secret store via the Linux Foundation. |
Its a very good idea, thanks ! |
|
My only concern with this is that i dont think there is a "universal" api that can be used, so if support is added for one, then everything would have to be added sort of thing. |
|
@boul2gom you got anywhere with this? wanted to see if you were still working on it so no duplicate effort is here I have a working demo of infisical and vaultwarden |
|
Following up on this request: I’ve built a working implementation and would like input on scope before opening any PRs Branch: https://github.com/goodelyfe/arcane/tree/feat/secret-sources (rebased on 2.16.0) What it doesA project can be bound to one or more secret sources. At deploy, Arcane fetches the variables and passes them to Compose for interpolation only. Values are never stored in Arcane's database, written to
Security model
Proposed split
Questions
AI disclosure: AI assisted (Claude) writing a bit of the code under my direction; I reviewed it and tested every provider listed above by hand in the dev environment. |
|
Greetings all. Following up on this |
|
You can open a PR for it, and ill try to review it as I have time. |
Uh oh!
There was an error while loading. Please reload this page.
Feature Description
Secrets managers support with abstract interface (to support Infisical, Doppler, etc in an agnostic way, without adding a lot of dependencies for each provider)
Problem It Solves
It's impossible to easily get credentials for shared databases, and use secrets rotation. Secrets and shared api keys (such as Resend ones) must be copy/pasted in every project, and its hard to maintain with multiple projects
Proposed Solution
1. An exec-resolver
2. A button on the with pre-configured provider api key in settings
This way allow user to pull project-associated env variables in its .env automatically
3. A lifecycle-hook
The hook must be edited in the project ui, maybe by splitting down the .env text field.
infisical export --path="/kener" --format=dotenv > .env4. An API, with webhooks
5. Binary plugins (as HashiCorp does)
Alternatives Considered
No response
Additional Context
No response
Would you be willing to work on this feature?
All reactions