LOG_LEVEL variable impacts downstream jobs

Currently, the LOG_LEVEL: info variable that is setup in the template that we reference in our ci pipeline configurations cause issues in our applications for unrelated CI jobs.

We setup our configuration based on the env var, which we expect to be unset.

config.log_level = ENV.fetch('LOG_LEVEL', 'warning')

Because the template sets this variable, it changes the log level for our CI jobs to a level we do not expect. Is there a solution where the renovate specific ci variable can be set to RENOVATE_LOG_LEVEL? Would I also need to place an issue in the GitHub renovate repository as well?

If this repo moved the configuration of LOG_LEVEL to the individual jobs, then it does not have an impact on downstream repositories that reference this template. For example:

.renovate
  variables:
    LOG_LEVEL: info