Brownouts and deprecation of config encryption in Mend-hosted Apps

[rarkins]

Tell us more.

The Mend apps (which power free Renovate for github.com, Bitbucket Cloud, and Azure DevOps) now support uploading Renovate secrets via the web UI at https://developer.mend.io

We will be discontinuing support for "encrypted": { ... }" config in these Mend apps early in the year. In practice this means we no longer populate the privateKey field in global config.

In the meantime, we will be be "browning out" the privateKey for hours at a time, in an effort to catch the attention of anyone who hasn't noticed the WARN messages in logs or dashboard. Those still using encrypted config will see this in an "Action Required: Fix Renovate Config" issue:

---

Location: config
Error type: Encrypted config unsupported
Message: This config contains an encrypted object at location $.encrypted but no privateKey is configured. To support encrypted config, the Renovate administrator must configure a privateKey in Global Configuration.

---

If you see this message then you need to follow the instructions at https://docs.renovatebot.com/mend-hosted/migrating-secrets/