Watcher for config updates
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
Issue: Feature Request
Is your feature request related to a problem? Please describe.
There are updates in the bench config files and are usually security related. But they get overlooked as the configs don't get regenerated automatically.
Describe the solution you'd like
Something that checks if there are config changes that haven't been applied to your bench. It hints you to regenerate the configs again. This can be triggered on certain bench command executions similar to https://github.com/frappe/bench/pull/960. Move these to a watcher functions list that execute on triggers perhaps.
Describe alternatives you've considered
None
Additional context
None
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the bench command execution paths and pull request #960, then identify how bench configs are generated and where watcher functions could run. Done means selected bench commands detect unapplied config changes and tell the user to regenerate them, without silently leaving security-related updates unapplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100