Add table github_dependency about steampipe-plugin-github HOT 16 CLOSED

Hey @captn3m0 , sorry for the radio silence on this one.

I haven't used https://github.com/shurcooL/githubv4 personally, but it looks promising and I'd be open to introducing that package to this plugin for better GraphQL querying support for new/existing tables. If that package isn't sufficient, I'd also be open to querying the GraphQL API directly, similar to what the lyft/cartography does, along with our Turbot plugin, e.g., https://github.com/turbot/steampipe-plugin-turbot/blob/main/turbot/table_turbot_resource.go.

If anyone is interested in trying to add new tables using the shurcool/githubv4 repo or hitting the GraphQL API directly, we'd be happy to work with them on the design process, review any incoming PRs, and answer any questions they have.

from steampipe-plugin-github.

@captn3m0 Thank you for raising this request, but as of now, there is no go API available for the above. We will check again after some time.

from steampipe-plugin-github.

The go-github library (currently being used) will not support the resource, since the resource is exclusive to the GraphQL API. It recommends using https://github.com/shurcooL/githubv4 instead. (See google/go-github#646 for eg)

Long term, every new resource from GitHub is being supported only on the GraphQL API, so it might be worth considering a switch. As another example, lyft/cartography uses the GraphQL API for GitHub resource discovery.

from steampipe-plugin-github.

@captn3m0 appreciate your interest and detailed information. Thank you!!. We will definitely be checking this. Pls, keep us posted for further observation.

from steampipe-plugin-github.

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

from steampipe-plugin-github.

not stale.

from steampipe-plugin-github.

Rest API support is on the GitHub roadmap now github/roadmap#495

from steampipe-plugin-github.

The item on roadmap only covers alerts and updates. The issue was for DependencyGraph which is much more comprehensive (all dependencies of a repo, irrespective of vulnerability status).

from steampipe-plugin-github.

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

from steampipe-plugin-github.

'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.'

from steampipe-plugin-github.

not stale

from steampipe-plugin-github.

Hey @captn3m0 , just so you're aware, we're not actively looking at adding this table as we're currently focusing on other priorities. I believe the resources and links I've included in my previous comment can help anyone looking to implement this table, but if not, we're happy to help/provide more guidance.

The stale label will be re-attached every 30 days as per our workflow, so if you'd like to keep this open for more community visibility, please feel free to continue commenting (just like above). Thanks!

from steampipe-plugin-github.

'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.'

from steampipe-plugin-github.

I've just updated the github_organization_member table to use the GitHub GraphQL API. If anyone's interested in adding the github_dependency table, I believe using the github_organization_member table is a good starting point.

from steampipe-plugin-github.

'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.'

from steampipe-plugin-github.

'This issue was closed because it has been stalled for 90 days with no activity.'

from steampipe-plugin-github.