The readme makes it difficult to know what the clients enable projects to do. We should break out separate getting started guides (one for nodejs and one for golang) as well as an overview of the system.

Currently https://api.deps.cloud responds with blank Not Found page. It could give a documentation page instead of the request comes from browser.

The README documentation is pretty bare and it would be good to get a few good code samples in each of them. This ticket is scoped to updating the README for packages/depscloud-api-python.

In https://github.com/depscloud/tracker/issues/69, I spec'd out the rough details for implementing searching on top of the database. This change should include the relevant proto changes and associated generated clients.

https://grpc-ecosystem.github.io/grpc-gateway/docs/v2-migration.html

grpc-ecosystem/grpc-gateway#1223

The README documentation is pretty bare and it would be good to get a few good code samples in each of them. This ticket is scoped to updating the README.md for Golang.

Should be pretty easy to do since the gRPC plugin is in place. Figuring out how to publish the pipi module is a different story.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update jest monorepo (@types/jest, jest)
• chore(deps): update golang docker tag to v1.20
• chore(deps): update actions/checkout action to v4
• chore(deps): update dependency typescript to v5
• chore(deps): update node.js to v16
• chore(deps): update node.js to v20
• fix(deps): update module github.com/grpc-ecosystem/grpc-gateway to v2
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency ts-jest to v26.5.6
• fix(deps): update module github.com/grpc-ecosystem/grpc-gateway to v1.16.0

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency grpcio to v1.53.0 [security]
• chore(deps): update dependency protobuf to v3.18.3 [security]
• fix(deps): update module google.golang.org/grpc to v1.56.3 [security]
• fix(deps): update module google.golang.org/protobuf to v1.33.0 [security]
• chore(deps): update dependency typescript to v4.9.5
• fix(deps): update dependency @grpc/grpc-js to v1.10.6
• fix(deps): update dependency @grpc/proto-loader to v0.7.12
• fix(deps): update module github.com/golang/protobuf to v1.5.4
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Noticed the other day that there is no CI/CD for this library. We should have at least two:

• branch build - run generation, ensure no changes, quick test
• tag build - publish to npm

Things appear to continue to function, but seems related to some changes I have out in a PR for python:

(node:26140) Warning: github.com/grpc-ecosystem/grpc-gateway/third_party/googleapis/google/api/annotations.proto not found in any of the include paths 

See depscloud/deps.cloud#19

• proto needs to be update to include source url
• .d.ts file needs to be updated to include source url field

Now that the swagger documentation is available on api.deps.cloud, we should add more documentation to the protobufs based on the service, functionality, and message bodies.

Ticket to track discussion around enhancements to this repository in v0.3. Some initial thoughts:

1. I'd like to keep this pinned to v1alpha.
2. Move generated code into language-specific sub-directories.
3. Put gRPC clients into a grpc directory.
4. Put REST clients into a rest directory.
5. Remove topology service.
6. Use more colloquial terms (group, name instead of organization, module)
7. Design a traversal api (https://github.com/deps-cloud/cli/issues/8)

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Under v1alpha, modify the schema to add new fields to facilitate the migration from v1alpha to v1beta. Notably, name on Module.

Right now, importing a client in nodejs requires a trailing suffix. It would be great if they only needed to import once. For example @deps-cloud/api/v1alpha/extractor instead of @deps-cloud/api/v1alpha/extractor/extractor

Here are a couple of goals:

• Start a "hard" break between graphstore definition and depscloud definitions
• Remove duplication of modules where possible
• Reduce number of imports
• Consolidate into fewer services
• Start to consider how we filter on edge data.

The README documentation is pretty bare and it would be good to get a few good code samples in each of them. This ticket is scoped to updating the README for packages/depscloud-api-nodejs.

We should have workflows to build and push the docker images.

On branches, docker images should be built. Since these are largely SDK containers, there isn't much to test about them. When the branch is main, we should push a :latest tag to dockerhub.

Part of: https://github.com/depscloud/tracker/issues/43

This is needed to restrict the datatypes returned by a traversal.

Since this project is largely generated, it would be good to ensure that the generation is happening properly. For example, when a change is checked in on any branch we should re-run code generation and look for a clean working tree. If files were modified, it's likely the code wasn't generated before commit.

In the event of an unclean working tree, the build should fail.

We will need some client side changes to allow clients to post older data to the API.

I managed to pull together a PR that supports indexing a handful of fields in our data model for better access... In order to access some of that information, we need some new apis added.