Add concept of syncing-network and use to filter actions resolvers and commands #1047
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed
syncingNetwork
column to theActions
table (and corresponding types and models)syncingNetwork
by adding--syncing
or-s
parameter to commands. --syncing can now be used to filter the following commands:actions get
,actions update
,actions delete
, andactions approve
.Example usage
The newly support --syncing (-s) option for actions modules commands extends current functionality to provide more expressive filtering of actions commands. Here are a few examples of using it in commands:
graph indexer actions get --syncing arbitrum-one
- Get all actions for deployments syncing data fromarbitrum-one
.graph indexer update --network arbitrum-one --syncing mainnet status queued
- Update the status for all actions for deployments syncingmainnet
data on thearbitrum-one
Graph Network.graph indexer actions approve --network arbitrum-one --syncing base
- Approve all actions on thearbitrum-one
network for deployments syncing data from thebase
network.