atlassian / atlassian/escalator
[Feature Request] Escalator auto reload configuration on change
- Dominant language
- Go
- Stars
- 685
- Forks
- 68
- Avg merge
- 47m
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
Updating escalator config currently requires a pod restart. We should update escalator to automatically read new config upon changing on disk.
**Describe the solution you'd like**
Check for changes in nodegroup config before each run. If safe to do so, run with the new config.
**Describe alternatives you've considered**
- Dynamically reading config from a NodeGroup CRD
- Not auto updating config
**Additional context**
This is useful for updates of escalator config without needing manual pod rotation.
Contributor guide
Research direction
Start by locating where Escalator loads its nodegroup configuration and where each run begins. Check how configuration changes on disk can be detected before a run, then verify that a safe updated configuration is used without restarting the pod; the existing behavior and relevant tests will show the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100