https://lakefs.io/ logo
Join Slack
Powered by
Small question lakefs configuration can take the f...
# help
o
Small question lakefs configuration can take the form of environment variables with 
LAKEFS_BLOCKSTORE_S3_REGION style. Do we have the same facility for lakectl IE have something like LAKECTL_CREDENTIALS_ACCESS_KEY_ID ?
i
Hi Ori, currently 
lakectl
doesn’t support env vars. It’s a cool feature though and I can see the value of adding it. Feel free to open up a feature request on Github or I can open one for you. Actually, @Guy Hardonag  tested it and since we’re using 
viper
 as our flags package, it is supported out of the box. For example, 
LAKECTL_CREDENTIALS_ACCESS_KEY_ID
 could be used if you export it. It also overrides the value from the 
lakectl.yaml
 config file.
o
Yes, I think this is important for consistency, it’s weird to have it for one and not the other. Opening a ticket.
👍 1
Oh and a followup .. is there a way to grab environement variables within the config file ? (any template syntax that works in there of the <%VALUE%> stile ?
Sorry for being lazy and not looking at the code. But you know it better.
i
See my updated comment - it actually does work!
o
Cool.. I love “auto closing tickets”. Is there a place to open documentation tickets ? (or I can just trust you ... : )
i
You can always trust us 😉 We use Github for all kind of tickets, Feature Requests / Bugs / Docs / etc.. We’ll reconsider separating them if it’ll get too messy.
o
... so it is workingish ....
Copy code
Error executing command: config file not found, please run "lakectl config" to create one
Config File ".lakectl" Not Found in "[/app]"
it is sufficient to have an empty .lakectl.yaml .. for it to work .. (and then the override from the environment works).
The same tested with
Copy code
bin/lakectl -c /tmp/lakectl.yaml auth users list
where lakectl.yaml is an empty file returns OK.
i
You’re right, creating a PR to allow no file at all so you’ll avoid the empty file hack.
3 Views
Open in Slack
PreviousNext
Powered by