lotus/node/config
Masih H. Derkani f273a440f0
Infer index provider topic from network name by default
Index provider integration uses a gossipsub topic to announce changes to
the advertised content. The topic name was fixed to the default topic
which is `/indexer/ingest/mainnet`.

In the case of lotus, the gossipsub validators enforce a list of topics
the instance is permitted to join by setting subscription filter option
when `PubSub` instance is constructed via DI.

Having the fixed topic name meant that any SP starting up a node on a
network other than `mainnet` would have to override the default config
to avoid the node crashing when index provider is enabled.

Instead of a fixed default, the changes here infer the allowed indexer
topic name from network name automatically if the topic configuration is
left empty.

Fixes #8510
2022-04-21 14:00:53 +01:00
..
cfgdocgen fix lint 2021-07-23 15:53:31 +02:00
def_test.go Infer index provider topic from network name by default 2022-04-21 14:00:53 +01:00
def.go Infer index provider topic from network name by default 2022-04-21 14:00:53 +01:00
doc_gen.go Infer index provider topic from network name by default 2022-04-21 14:00:53 +01:00
doc_util.go feat: config: Persistent subsystem log level config 2022-03-10 14:44:56 +01:00
dynamic_config.go move DealmakingConfiger and SealingConfiger away from config/types.go 2022-03-03 16:51:47 +01:00
load_test.go feat: Add additional test annotations (#8272) 2022-03-16 18:37:34 +01:00
load.go feat: config: Persistent subsystem log level config 2022-03-10 14:44:56 +01:00
storage.go feat: storage: Parallel proving checks 2022-03-29 11:45:08 -04:00
types.go Infer index provider topic from network name by default 2022-04-21 14:00:53 +01:00