Change Details

## Summary Several extensions (IPInfo, AbuseFilter) currently read from the NodeJS IPoid instance via Extension:IPReputation. These extensions expect the data to appear in a certain format. IPoid OpenSearch uses the default data format provided in the Spur.us data feed. In this epic, we will: * Add configuration and code to allow for switching between data sources (so that we can keep NodeJS IPoid as a backup, for at least some period of months) * Create a migration layer to convert the OpenSearch data format into the data format that NodeJS IPoid currently provides * Update extension code to use the OpenSearch data format ## Acceptance criteria - TBC

## Summary Several extensions (IPInfo, AbuseFilter) currently read from the NodeJS IPoid instance via Extension:IPReputation. These extensions expect the data to appear in a certain format. IPoid OpenSearch uses the default data format provided in the Spur.us data feed. In this epic, we will: * Add configuration and code to allow for switching between data sources (so that we can keep NodeJS IPoid as a backup, for at least some period of months) * Update extension code to use the OpenSearch data format

## Summary Several extensions (IPInfo, AbuseFilter) currently read from the NodeJS IPoid instance via Extension:IPReputation. These extensions expect the data to appear in a certain format. IPoid OpenSearch uses the default data format provided in the Spur.us data feed. In this epic, we will: * Add configuration and code to allow for switching between data sources (so that we can keep NodeJS IPoid as a backup, for at least some period of months) * Create a migration layer to convert the OpenSearch data format into the data format that NodeJS IPoid currently provides * Update extension code to use the OpenSearch data format ## Acceptance criteria - TBC