Summary
In our public repositories, we use SONAR_TOKEN, but in our private ones, this secret comes from SONARQUBE_GITHUB.
This secret is used in https://github.com/exasol/python-toolbox/blob/main/.github/workflows/report.yml#L42.
We could add this to the BaseConfig and switch the template to use a Jinja variable. Relevant entry points:
Decision Points
- Decide if we want to hard-code the two allowed options & have users flip between them or just allow private repos to change the string.
To Dos
Summary
In our public repositories, we use
SONAR_TOKEN, but in our private ones, this secret comes fromSONARQUBE_GITHUB.This secret is used in https://github.com/exasol/python-toolbox/blob/main/.github/workflows/report.yml#L42.
We could add this to the
BaseConfigand switch the template to use a Jinja variable. Relevant entry points:We could add the SONAR_TOKEN_NAME either as property which is overridden or as an input into the
BaseConfigclass.We need for this to be added to the dictionary output of
github_template_dictWe update this line to use the value added to the
github_template_dictDecision Points
To Dos
SONAR_TOKEN_NAMEintoBaseConfig; use the publicSONAR_TOKENas the default value. Then only private repos would need to override it.report.ymltemplate to use theSONAR_TOKEN_NAME