How to warn users about not supporting encrypted tokens in the Hosted-App

[nabeelsaabna]

Tell us more.

In the developer.mend.io hosted app we aim to deprecated the use of encrypted tokens in repository config (e.g. renovate.json) and for that a added a the ability to save/migrate secrets in the UI (no more privateKey)

Suggested solution:
Add a new self-hosted config option privateKeyWarning that will be printed once with warn level if a an encrypted token is found during the run

[rarkins]

Could be privateKeyWarning or encryptedWarning.

Ideally the warning message is displayed in each PR plus in the Dependency Dashboard

[PhilipAbed]

I'm having a bit of trouble implementing it on every PR

1. configuration is decrypted and validated early. i can do a print there, and it appears in the dashboard in repoProblems.
2. the warnings for every PR come from branch config/lookup warnings, by the time i reach there the 'encrypted' key is already deleted. so i need to send an indication in the config that 'encrypted' was detected + the flag is on, but anyway i think of doing this seems messy.
   i'm able to use the extractRepoProblems only without adding anything.

do we need this warning to appear on every PR?

[PhilipAbed]

i have tried to do it anyway
and i noticed that we have 2 Warnings sections, 1 for config warnings, the other for dependency lookup warnings
The other warning under the yellow Warning is for dependency lookup.
the flag is set to encryptedWarning: type something here see:
and the Configuration Warning is the topic of the warning i hardcoded

[PhilipAbed]

1. i can either show the Full Message with Topic + Message like you see in the picture.
2. show the message under the yellow warning
3. just write under the Warning in yellow, ask the user to look for errors in the dashboard

[justo-mend]

Text to show on the PR: "Warnings were raised when the job ran. See the Dashboard issue for more details."

[PhilipAbed]

in order to be consistent with the above message(See screenshot),
i used:
Warnings were raised. Check the logs or Dashboard for more information.