Add a setup check that tries to find indications of multiple `secret` values having been in-use
Open
Nobody has claimed this yet.
0. Needs triage
enhancement
feature: authentication
feature: settings
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Sometimes secret values have been lost / changed in some environments without the operator realizing the significance. Since this will cause problems, maybe we can detect signs of this in a set-up check.
e.g some of the people experiencing #34012
P.S. The next step after a setup check might be a documented process/tool to help people clean up after something like this happens.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reviewing issue #34012 and the existing setup-check context, then define what evidence of multiple secret values can be detected and what a successful check should report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100