graphprotocol / graphprotocol/indexer

Add syncing network to actions table and use to add syncing network support in indexer-cli commands

Open
#1,026 0 comments 0 reactions 1 assignee View on GitHub

@fordN is already working on this.

Since Nov 14, 2024.

indexer-cli
Dominant language
TypeScript
Stars
262
Forks
148
PR merge metrics
No merged PRs in 30d

Description

Background

Often subgraph deployments can be effectively grouped using the syncing network, so it would be useful for indexers to be able to use that field when defining and executing allocation strategy.

Todo

  • Add syncing_network to the Actions and IndexingRules tables
  • Update indexer-cli commands to use syncing_network for additional control:
    • graph indexer actions update ... should support a --syncing-network filter parameter
    • graph indexer actions approve ... should support a --syncing-network filter parameter
    • graph indexer allocations get ... should support a --syncing-network filter
    • graph indexer rules get .. should support a --syncing-network filter (indexer rules set.. likely won't need updating)
  • Can we query the graph-node's supported networks in order to be more intelligent about not trying to allocate/sync deployments the graph-node isn't configured to support?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.