Should st2timersengine default to local timezone?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
Curious why it's necessary to configure the timezone of the timers engine, instead of simply defaulting to the timezone of the local system?
Looking at the code, it doesn't seem to matter what the timezone is, because the timers are using the timezone from the rule definition.
I'm asking for puppet-st2. Is this an essential config option, or is it OK to be defaulted to America/Los_Angeles everywhere?
ISSUE TYPE:
- Feature Idea
STACKSTORM VERSION
2.9dev
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
Start by locating the st2timersengine timezone configuration and the timer handling for rule definitions. Compare the configured timezone with the local system timezone and determine whether the configuration is essential. Done requires a maintainer decision and a clearly specified defaulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100