Configuring GOPROXY with Mend-hosted Renovate?

[haines]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

We are using River Pro, which is distributed as a private Go module. To fetch it, we need to set GOPROXY and GONOSUMDB.

I tried to configure these in my renovate.json as

"env": {
  "GOPROXY": "https://proxy.golang.org,https://river:{{ secrets.RIVER_PRO_SECRET }}@riverqueue.com/goproxy,direct",
  "GONOSUMDB": "riverqueue.com/riverpro"
}

but sadly

Env variable name GONOSUMDB is not allowed by this bot's allowedEnv., Env variable name GOPROXY is not allowed by this bot's allowedEnv.

Is there any way for me to configure these settings without switching to self-hosted Renovate?

Logs (if relevant)

Logs

INFO: Repository has invalid config
{
  "error": {
    "validationSource": ".github/renovate.json",
    "validationError": "The renovate configuration file contains some invalid settings",
    "validationMessage": "Env variable name `GONOSUMDB` is not allowed by this bot's `allowedEnv`., Env variable name `GOPROXY` is not allowed by this bot's `allowedEnv`.",
    "message": "config-validation",
    "stack": "Error: config-validation\n    at mergeRenovateConfig (/usr/local/renovate/lib/workers/repository/init/merge.ts:200:19)\n    at processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at getRepoConfig (/usr/local/renovate/lib/workers/repository/init/config.ts:14:12)\n    at initRepo (/usr/local/renovate/lib/workers/repository/init/index.ts:56:12)\n    at Object.renovateRepository (/usr/local/renovate/lib/workers/repository/index.ts:64:14)\n    at attributes.repository (/usr/local/renovate/lib/workers/global/index.ts:206:11)\n    at start (/usr/local/renovate/lib/workers/global/index.ts:191:7)\n    at /usr/local/renovate/lib/renovate.ts:19:22"
  }
}

[rarkins]

We should have support for this within the next week once we add globalExtends: ['global:safeEnv'] to the hosted bot config.

Cc @nabeelsaabna