Adrian Rumpold02/28/2023, 9:01 AM
setting, but haven't been able to figure out exactly how to use it. Is there any documentation besides the configuration reference guide?
In particular, I'm unsure how to pass authentication credentials to the fallback backend: If I specify credentials that don't exist in lakeFS but are valid on the fallback S3 endpoint, I get an
error returned by the
command. If I specify the lakeFS credentials and try to access a bucket that would be handled by the fallback case, I get an
Do the credentials need to be identical for both the lakeFS S3 endpoint and the fallback?
Thanks for your help! 🙏
Itai Admi02/28/2023, 9:37 AM
Error: required flag(s) "user-name" not set
lakefs superuser [flags]
--access-key-id string create this access key ID for the user (for ease of integration)
-h, --help help for superuser
--secret-access-key string use this access key secret (potentially insecure, use carefully for ease of integration)
--user-name string an identifier for the user (e.g. "jane.doe")
Adrian Rumpold02/28/2023, 9:55 AM
Adrian Rumpold02/28/2023, 11:13 AM
resources. However, Flyte also puts its own metadata into the same S3 endpoint, which we obviously don't want to end up in lakeFS.
So we could either add an S3 request router in front of lakeFS, or use the fallback feature in lakeFS.
Adrian Rumpold02/28/2023, 12:44 PM