This message was deleted.
# secoda-support
w
This message was deleted.
e
It will help us to parse lineage information between Looker views and Snowflake tables.
👍 1
a
Are there any plans to set this up with a Looker deploy key instead of uploading the repo?
e
Could you elaborate on the Looker deploy key. How do you imagine we could use it to replace this current method? The reason why we chose this method is because to integrate with a GitHub repo you need to provide full access (read, write, delete) just to look at the file contents. So we thought most people would not want to give us that level of access to their repos.
a
Select Star has an option to add a deploy key into the Looker repo without write access. That's how they parse lineage information, might be worth looking into!
e
That’s helpful feedback, thanks Kyle. We will definitely look into that method!
a
I didn't upload the LookML repo but it looks like Secoda is still able to parse lineage? Is the Repo for lineage between Looker and our database?
e
It’s able to parse lineage within Looker, so between views, explores, and dashboards. You’re correct that the repo is for lineage between looker and the database.
👍 1