Extract Alerts configuration

[fmrsabino]

• The Alerts related configuration and environment keys were extracted to the AlertsApiModule and AlertsControllerModule.
• By separating the properties of the Alerts feature to its own configuration object which is loaded dynamically, we can make some properties set as required in the application only if the respective feature is loaded.
• This effectively reduces the number of configuration properties that is needed to set for the application to launch, when features are under development or a set of features is not needed by the hosting party.
• In order to avoid key collision, the feature level configuration now uses namespaces (with registerAs).
  • alerts-api for keys used in /datasources/alerts-api
  • alerts-route for keys used in /routes/alerts

classDiagram
    ConfigurationModule ..> rootConfiguration
    AlertsApiConfigurationModule ..> alertsApiConfiguration
    AlertsConfigurationModule ..> alertsConfiguration
    NestConfigService o-- ConfigurationModule
    NestConfigService o-- AlertsApiConfigurationModule
    NestConfigService o-- AlertsConfigurationModule
    IConfigurationService -- NestConfigService
    FeatureA ..|> IConfigurationService
    FeatureB ..|> IConfigurationService
    FeatureC ..|> IConfigurationService

    <<Interface>> IConfigurationService
    <<Service>> NestConfigService
    <<Module>> ConfigurationModule
    <<Module>> AlertsApiConfigurationModule
    <<Module>> AlertsConfigurationModule

    note for AlertsApiConfigurationModule "Only loaded if feature flag is set to true"
    note for AlertsConfigurationModule "Only loaded if feature flag is set to true"

    class IConfigurationService {
    }
    class NestConfigService {
    }
    class ConfigurationModule {
    }
    class rootConfiguration {
        about
        applicationPort
        ...
    }
    class AlertsApiConfigurationModule {
    }
    class alertsApiConfiguration {
        apiKey
        baseUri
        account
        project
    }
    class AlertsConfigurationModule {
    }
    class alertsConfiguration {
        signingKey
    }

[coveralls]

Pull Request Test Coverage Report for Build 8644648086

Details

• 36 of 40 (90.0%) changed or added relevant lines in 10 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 92.88%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/datasources/alerts-api/configuration/alerts-api.configuration.ts	5	7	71.43%
src/routes/alerts/configuration/alerts.configuration.ts	5	7	71.43%

Files with Coverage Reduction	New Missed Lines	%
src/routes/transactions/entities/tests/human-description.builder.ts	1	90.0%

Totals
Change from base Build 8619148770:	-0.01%
Covered Lines:	6727
Relevant Lines:	6986

---

💛 - Coveralls

[fmrsabino]

This was set to false because otherwise, every test would have to include the now optional Alerts configuration (resulting in more changes).

Since this feature is opt-in, each test should decide if it should include the feature or not.

[hectorgomezv]

👏🏻