Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Good secrets management in Eka #2

Open
ic4-y opened this issue Aug 21, 2024 · 0 comments
Open

Good secrets management in Eka #2

ic4-y opened this issue Aug 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ic4-y
Copy link

ic4-y commented Aug 21, 2024

I thinks it's imperative that we think of managing secrets from the beginning. There are multiple dimensions to this I see intuitively. At least these two here

  1. We might support something like sops to populate secrets in eka.toml. This would be different from using sops-nix to populate secrets on NixOS systems / home configurations . But maybe we can find a smart way to hook into the first layer of sops to make things like sops-nix superfluous? Not sure.

  2. Builder endpoints like I proposed in Refine CLI core structure #1 might need authentication of various kinds, from simple HTTP authentication to JSON webtokens, to other tokens (like biscuit tokens).

Let's keep track of what we need / want to implement and in what order via this issue.

@ic4-y ic4-y added the enhancement New feature or request label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant