| `DEFECTDOJO_SONARQUBE_APPLICATION` | your application name in Sonar | ex: project-name |
| `DEFECTDOJO_SONARQUBE_PROJECT_KEY` | your project key in Sonar (be careful, the project key might be distinct from project-dir-project-name, sometimes Sonar adds a suffix) | ex: project-dir-project-name or project-dir-project-name__AXjLJ76cpGZrj3BUYg10 |
| `DEFECTDOJO_SONARQUBE_SINCELEAKPERIOD`| determines if delta analysis is activated | false |
| `TBC_VAULT_IMAGE` | The [Vault Secrets Provider](https://gitlab.com/to-be-continuous/tools/vault-secrets-provider) image to use (can be overridden) | `registry.gitlab.com/to-be-continuous/tools/vault-secrets-provider:master` |
| `VAULT_BASE_URL`| The Vault server base API url | _none_ |
| `VAULT_OIDC_AUD`| The `aud` claim for the JWT | `$CI_SERVER_URL` |
| `vault-base-url` / `VAULT_BASE_URL` | The Vault server base API url | _none_ |
| `vault-oidc-aud` / `VAULT_OIDC_AUD` | The `aud` claim for the JWT | `$CI_SERVER_URL` |
| :lock: `VAULT_ROLE_ID` | The [AppRole](https://www.vaultproject.io/docs/auth/approle) RoleID | **must be defined** |
| :lock: `VAULT_SECRET_ID` | The [AppRole](https://www.vaultproject.io/docs/auth/approle) SecretID | **must be defined** |
@@ -197,7 +222,7 @@ Then you may retrieve any of your secret(s) from Vault using the following synta