Connector Improvement: Fivetran Snyk connector issue - dependency link
AnsweredFor Fivetran's Snyk connector with data relationships shown here https://fivetran.com/connector-erd/snyk there are no ways to cross link tables such as issue or issue_problem with dependency or dependency_with_issue. Since the issue and issue_problem tables only have opaque IDs of the issue, users of the connector data are unable to find the actual original package name. Meaning we can see there is an issue/finding, when it was created, the current status, etc. but not what the name of the dependency that's affected which is the most important piece. Please implement a foreign key across issues/issue_problem and dependency/dependency_with_issue or add that data for the package/dependency name directly to the issue/issue_problem tables such that a query can be run that either directly produces or cross joins tables to produce data about a particular package.
-
Official comment
Hi Holger,
Thanks for raising this - it’s a great callout, and we completely agree with the need for better cross-linkability between issues / issue_problem and the dependency / dependency_with_issue tables in the Snyk connector.We’ve added this enhancement request to our backlog, and we expect to include it in one of our upcoming sprints. Improving the ability to surface the actual affected package name is important for downstream usability, and your input helps us prioritize it appropriately.
Really appreciate you highlighting this!
Best,
Sisan
Please sign in to leave a comment.
Comments
1 comment