docs: added docs for migrating encrypted secrets #30132
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…now to be stored in App settings.
docs: new doc for Mend App secrets and secrets migration
Merge from main fork
rarkins
requested changes
Jul 11, 2024
HonkingGoose
suggested changes
Jul 11, 2024
There was a problem hiding this comment.
I changed a whole lot! So please double check that the information is technically correct.
The docs has text about the confirmation box at the final step of importing a secret. It basically says that the reader should check the message carefully, to see if their secret is in "state A" or "state B". That kind of information must go in the confirmation box itself, in clear words.
At the end, as user you want to know:
- Can Renovate see/use my secret now?
- Is my secret still safe?
- Is this what I expected to happen? If not, how can I get what I want?
The web UI should guide and help the user through the process. The docs are supporting material.
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
rarkins
previously approved these changes
Jul 20, 2024
HonkingGoose
suggested changes
Jul 20, 2024
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
rarkins
previously approved these changes
Jul 20, 2024
|
@justo-mend in future please don't submit PRs from your |
rarkins
reviewed
Jul 20, 2024
rarkins
approved these changes
Jul 20, 2024
|
🎉 This issue has been resolved in version 37.437.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Updated docs to show how to migrate encrypted secrets.
Context
Storing encrypted secrets in Renovate config is deprecated and will no longer be supported from 01-Sep-2024. New docs have been added to show how to migrate encrypted secrets from Renovate config to the App settings via the web UI.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: