Add allow_world_readable_secrets option to config file #663
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#663
Loading…
Reference in a new issue
No description provided.
Delete branch "PicNoir/garage:nin/world-readable-conf-file"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Paired on that with @flokli.
I also took the liberty to add clang to the default devshell. We can't build Garage without it.
This is my first contribution to Garage, I've been shy and tried not to set the house on fire the first time I visit it. I think we should extract the current
GARAGE_ALLOW_WORLD_READABLE_SECRETS
env variable "ad-hoc" management to clap. Aside from clarity, it'd document the variable in the--help
usage for free. I can add that to this PR if you think it's a good idue.Fixes #658
045fb89082
to930fa08395
rpc_secret_file
,metrics_token_file
andadmin_token_file
using environment variables #643Could you make this change on the
main-0.8.x
branch instead of themain
branch? PR #643 is also on that branch but I think the history you worked on does not include it so that will cause problems. I will sync the two branches manually when making the next release, but for now let's keep all the changes concerning env variables and cli flags on the 0.8.x branch.By switching to
main-0.8.x
you can also remove theclang
that you added in the flake.nix and we will make that a separate PR.Yes it's a good idea, feel free to do so. It will probably require a bit of refactoring between
garage/main.rs
andgarage_util/config.rs
Isn't this bug also affecting 0.9.0 too? I'd assume
main
should contain all fixes, and we backport from there…I'm doing the opposite, it's not backporting but "forward-porting" :D
Changes that can be applied to the 0.8.x codebase are done on branch
main-0.8.x
, and then I merge that branch into branchmain
to have all changes in the 0.9 release as well. This helps me keep track in the git history of the fact that the 0.8.x code is an ancestor of the 0.9.x code (in the commit graph sense).930fa08395
tof83fa02193
Rebased on
main-0.8.x
. Having a stab at the clap refactoring discussed two messages above.Quick status update: started refactoring the thing, but got interrupted midway through. Just put that first thing on tomorrow's todolist.
Hello, can anyone remember the status of this work? I'm going to make a v0.8.5 and v0.9.1 release asap and it would be great to have this included if it is ready.
I will merge this as-is for now, thanks for the contribution @PicNoir and @flokli !
Damn, I completely missed these messages. Sorry, for not responding: I did not receive any notification.
I have a half-baked refactoring I was talking about above. It required more modifications than I first expected, I had to move around a lot of things.
Anyways, even if it's sub-optimal, I guess this is fine-ish as it is.
Edit: pushed the WIP there https://git.deuxfleurs.fr/PicNoir/garage/src/branch/pic-refactoring just in case it'd be useful to somebody. It's definitely not ready though.