-
Notifications
You must be signed in to change notification settings - Fork 109
Open
Labels
Description
Is your feature request related to a problem? Please describe.
Each config.yaml
file for a processor appears to be intended for only one processor. At least, I haven't figured out the sytax for adding more than one processor into a processor config file. It's not quite clear what is the best way to run all the processors we need, eg
`account_restoration_processor`, `account_transactions_processor`, `ans_processor`, `default_processor`, `events_processor`, `fungible_asset_processor`, `user_transaction_processor`, `stake_processor`, `token_v2_processor`, `objects_processor`, `monitoring_processor`, `gas_fee_processor`, `parquet_default_processor`, `parquet_objects_processor`, `parquet_user_transaction_processor`, `parquet_events_processor`, `parquet_ans_processor`, `parquet_fungible_asset_processor`, `parquet_transaction_metadata_processor`, `parquet_account_transactions_processor`, `parquet_token_v2_processor`, `parquet_stake_processor`
Describe the solution you'd like
Create a script or other method to run all the processors needed, so a GraphQL endpoint can be spun up with all desired queries successful.
Describe alternatives you've considered
- Running the processors from the
movement
repository via feat: implement indexer processors v2 #1264 (failed as the Movement node does not settable_item
) - Attempting to connect directly to the Indexer FN without the use of the GrpcManager or DataService... it seems all components of the self-hosted transaction stream service may be necessary.
Additional context
Add any other context or screenshots about the feature request here.