https://lakefs.io/ logo
#help
Title
# help
n

Nacho Corcuera

01/11/2024, 9:45 AM
Hi all! I am trying to set up some CI/CD pipelines. The idea is to use lakectl for creating the branches and doing the commits. I have seen that there is --config for passing a YAML file with the configuration avoiding to do a lakectl config in the initial set up. Is there a way to pass the access_key, secret_key and endpoint directly to lakectl without constructing a YAML file? Thanks!
o

Oz Katz

01/11/2024, 9:48 AM
Hi 👋 If you prefer, you can pass all the necessary configuration as environment variables. see the last paragraph on this section of the reference
n

Nacho Corcuera

01/11/2024, 10:01 AM
I don't want to have preloaded environment variables with the secret_key and access_key. Can it be passed on fly? without making the set up variables?
o

Oz Katz

01/11/2024, 10:08 AM
You can pass these variables on the fly, you don’t have to preload them, e.g.
Copy code
LAKECTL_SERVER_ENDPOINT_URL="…" lakectl branch list …
or perhaps im missing something? 🙂
n

Nacho Corcuera

01/11/2024, 10:48 AM
No, i was thinking on a way of passing credentials by the cmd like --access_secret_key or something like that
Okey, so just for summarize. Basically for using them as ENVIRONMENT variables, i have to just put LAKEFS_{name_of_variable}. Am i right?
o

Oz Katz

01/11/2024, 11:13 AM
For lakectl you would use LAKECTL_ as a prefix, correct