Add validation of CI input

Problem to solve

We usually only run pipelines by pushing into a branch and through the scheduled ones. This makes the combination of possible variables in the CI to be stable and consistent, if it works once it will always work (unless the CI files change).

But, some times we might want to modify some variables to test something different/concrete. To do this we introduce the human factor, which might introduce a typo/or misconfigure a variable. This causes the pipeline to fail in an intermediate step without a clear reason on why it failed making it necessary to investigate what happened when it could have been detected by the system. This will also waste computational resources for nothing and can cause to get rate limits on external dependencies.

Stakeholders

• CTA Dev Team

Proposal

Add a stage that validates all the input variables before anything else.