In "Refine ppss.yaml for closer 1:1 mapping to bots" #451, the yaml file got reworked. The big change was: each module got its own "ss" module, with parameters specified via a sub-section of ppss.yaml. Then, most modules got their own way to specify feeds. Because modules earlier in the flow may have more feeds (eg ohlcv data factory), and modules later on may have fewer (eg predictoor).
Exception: one module isn't done yet: publisher. That's the goal of this issue.
Specifically, to specify to publisher what feeds to publish, we need to move from its status quo of hardcoded list of feeds, to a list of feeds specified in publisher_ss.
Then, publisher module needs to read in publisher_ss.feeds, and choose what to publish based on that.
Publisher will not be doing subgraph queries from existing feeds. Rather, it is publishing new feeds.
Note that most module ss's inherit a base ss in order to get feeds functionality in a single line. We should be able to do the same thing here. Of course we still need to update publisher behavior, and add tests.
TODOs
[ ] Update ./ppss.yaml to have example feeds in publisher_ss section
[ ] Update publisher_ss to handle feeds
[ ] Update publisher to use publisher_ss feeds (and deprecate old hardcoded way)
trentmc
commented
9 months ago
Parent: [EPIC: YAML] Add YAML & CLI. "v0.2" of Predictoor #400
Background / motivation
In "Refine ppss.yaml for closer 1:1 mapping to bots" #451, the yaml file got reworked. The big change was: each module got its own "ss" module, with parameters specified via a sub-section of ppss.yaml. Then, most modules got their own way to specify feeds. Because modules earlier in the flow may have more feeds (eg ohlcv data factory), and modules later on may have fewer (eg predictoor).
Exception: one module isn't done yet: publisher. That's the goal of this issue.
Specifically, to specify to publisher what feeds to publish, we need to move from its status quo of hardcoded list of feeds, to a list of feeds specified in publisher_ss.
Details:
In ppss.yaml, there is already:
A
feedssection needs to get added to that:Then, publisher module needs to read in publisher_ss.feeds, and choose what to publish based on that.
Publisher will not be doing subgraph queries from existing feeds. Rather, it is publishing new feeds.
Note that most module ss's inherit a base ss in order to get
feedsfunctionality in a single line. We should be able to do the same thing here. Of course we still need to update publisher behavior, and add tests.TODOs