You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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.
The text was updated successfully, but these errors were encountered:
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
We might support something like
sops
to populate secrets ineka.toml
. This would be different from usingsops-nix
to populate secrets on NixOS systems / home configurations . But maybe we can find a smart way to hook into the first layer ofsops
to make things likesops-nix
superfluous? Not sure.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.
The text was updated successfully, but these errors were encountered: