Make tapSubgraph to be an optional value

[carlosvdr]

Ford found out tapsubgraph is not an optional value so changed a few things to make it work

[aasseman]

It's a quick solution, LGTM.

Longer term it'd be nice to have a cleaner solution. In particular it'd be nice to warn the indexer if we see RAVs in the DB but we don't have the right settings to act on them.

[fordN]

Nice, thanks for the quick fix! 🙏

There is still another backwards compatibility issue with the TAP integration though. If the indexer-agent is connected to a network without TAP contracts deployed it fails to startup: runs into an unhandled promise rejection. I'll create an issue to track and we can resolve in a subsequent PR.

[fordN]

LGTM! Once it's confirmed working for an indexer without tapSubgraph configured let's get merged in.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
12241928	Triggered	Generic High Entropy Secret	e78f269	network-configs/config.yaml	View secret
12251296	Triggered	Generic High Entropy Secret	e78f269	network-configs/config.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}