Addition of SUPPRESS_ALERTS environmental variable

[Lenbkr]

What did we change?

Why are we doing this?

How was it tested?

• Locally
• Development Environment
• Not needed, changes very basic
• Husky successfully run
• Unit tests passing and Documentation done

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[Justus-at-Tazama]

I can't seem to get this to work. I've deployed the cms-service in the Docker stack with a subject of cms. I tested this for the typology processor change and it was posting to the cms subject just fine.

I had a look through the code and noticed that the post to the NATS server is not explicitly taking in the optional parameter for the configuration.producerStream parameter set up in the .env:

https://github.com/frmscoe/transaction-aggregation-decisioning-processor/blob/a54ae1c986c959f2b0cffaccdeb9eeda1fb61ce9/src/services/logic.service.ts#L69

I compared the implementation of this NATS interaction with the one in the typology processor and they're quite different. Compare:

typology processor

    if (!configuration.suppressAlerts && isInterdicting) {
      // Send Typology to CMS
      const spanCms = apm.startSpan(`[${transactionId}] Send Typology result to CMS`);
      server
        .handleResponse({ ...tadpReqBody, metaData }, [configuration.cmsProducer])
        .catch((error) => {
          loggerService.error('Error while sending Typology result to CMS', error as Error, logContext, msgId);
        })
        .finally(() => {
          spanExecReq?.end();
          spanCms?.end();
        });
    }

tadproc

      if (!configuration.suppressAlerts) {
        const result: CMSRequest = {
          message: `Successfully completed ${typologies.length} typologies`,
          report: alert,
          transaction,
          networkMap,
        };

        result.report.tadpResult.prcgTm = CalculateDuration(startTime);
        await server.handleResponse(result);
      }

The typology processor explicitly passes the configured cms subject, the tadproc does not.