• T. P.

    T. P.

    1 year ago
    again, in context of k8s, secrets are not really good for gitops so you can look into using: • sealed secrets: https://github.com/bitnami-labs/sealed-secrets (uses key pair and gitops safe) • or hasicorp vault https://www.vaultproject.io/ for proper security, authentication, life cycle management of secrets etc.
    T. P.
    m
    2 replies
    Copy to Clipboard
  • c

    Christophe Benz

    1 year ago
    Hi! First question 😃 I'd like to know if it's possible to insert commits before some other. Or in other words, to rebase a branch. My use case : I plan to track data changes in lakefs, creating commits, and besides I have a git repo that has existed for many years about that same data, with commits too. I'd like to import those git repo commits before the lakefs repo commits. Context : I work for the free software project db.nomics.world (macro economics time series aggregator) that uses git and is switching to object storage, and why not lakefs.
    c
    Oz Katz
    3 replies
    Copy to Clipboard
  • a

    Andor Markus

    1 year ago
    Hi Team, Please can you finish the EMR guide? https://docs.lakefs.io/using/emr.html Its empty now
    a
    1 replies
    Copy to Clipboard
  • a

    Andor Markus

    1 year ago
    Hi Team, In the architecture documentation lakeFS needs RDB for metadata indexing. In the current implementation it needs PostgreSQL server. AWS aurora serverless V1 supports MySQL and PostgreSQL language. The more powerful aurora serverless V2 only supports (currently) MySQL. Is it possible to extend the RDB support to MySQL as well? Thanks, Andor
    a
    1 replies
    Copy to Clipboard
  • Jai Jagani

    Jai Jagani

    1 year ago
    We are trying do download a file from lakefs repo branch with python .. no documentation present for that on https://docs.lakefs.io/integrations/python.html Any help really appreciated
    Jai Jagani
    Guy Hardonag
    +2
    34 replies
    Copy to Clipboard
  • Christian Fobel

    Christian Fobel

    1 year ago
    Hi all, I am new the lakeFS Slack group. I just noticed that there is a broken link cross-table consistency link in the "Hudi, Iceberg and Delta Lake: Data Lake Table Formats Compared" blog post; I think it should maybe point to here? https://docs.lakefs.io/usecases/production.html#example-3-cross-collection-consistency
    Christian Fobel
    1 replies
    Copy to Clipboard
  • t

    Thomas Vander Wal

    1 year ago
    Hey LakeFS team, I’m wondering if there is any interest in supporting an SSL certificate env variable for the
    lakectl
    utility. I did get a workaround here but as more of our users get interested in the service it would make integration a bit easier for a few reasons. 1. often users at an enterprise don’t have admin rights on their computer to do the fix 2. Makes a similar setup for users on different os 3. Follows similar patterns such as
    kubectl
    ,
    awscli
    , and pythons requests package.
    t
    Oz Katz
    3 replies
    Copy to Clipboard
  • mishraprafful

    mishraprafful

    11 months ago
    Hi LakeFS team, What do you think about having an
    ignore
    file for upload command for lakeFS? Let me know if this possible as of now somehow? To add more context, we are using lakeFS in a way that is highly integrated with one’s GitHub repository. As a part of the workflow, one uses the
    lakeFS upoad --recursive
    command to update the data. Do you think it makes sense to have an ignore option with the command that can be pointed to an
    .ignorefile
    ?
    mishraprafful
    Oz Katz
    6 replies
    Copy to Clipboard
  • Romain

    Romain

    11 months ago
    Hi team, I have added a feature request as an issue in the repo, I hope it's ok to post it there: https://github.com/treeverse/lakeFS/issues/2545
    Romain
    1 replies
    Copy to Clipboard
  • y

    Yusuf K

    8 months ago
    This is a very high level suggestion and not sure it would work but just my feedback. While I was working with lakefs I felt like I was really missing the git experience of having a current relative position in the tree. For example when I do a
    git add .
    it's relative to the branch I'm on at that time. Whereas the equivalent command in lakefs that moves data from work space to staging,
    lakectl ingest --from --to
    doesn't share that same convenience. Its more flexible, but it would be nice to be able to do something like a
    lakefs init
    such that when I create a new branch it defaults the source to the current branch etc.
    y
    1 replies
    Copy to Clipboard