Skip to content

Add an environment variable to start allureCollector and resultAggregator services

Current situation

Currently, allure reports are generated automatically with each workflow. HTML reports have been implemented and are recommanded for their versatility and possible customization. Allure reports should be deprecated.

Desired outcome

For the first step in this deprecation, by default the allure reports should stop being generated each and every time, but there should be an option to reactivate the creation of allure reports when deploying /updating the Orchestrator from now on.

The orchestrator needs to be deployed using a new environment variable like OPENTF_ALLURE_ENABLED.

  • If the environment variable is specified, the behaviour should be the same as with the previous version : the publisher emits allureCollectorInput and the services allureCollector and resultAggregator need to be started so the allure reports can be generated and sent to squash TM.
  • If the environment variable is not specified, it should be interpreted as disabled : the publisher needs to stop emitting allureCollectorInput. The services allureCollector and resultAggregator should not be started.