Opened 12 years ago
Last modified 11 years ago
#40 new enhancement
Add support for scheduled changes
Reported by: | Kris Deugau | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.2 |
Version: | Keywords: | ||
Cc: |
Description
Changes can be set to go live at a certain time, so that overworked systems/NOC staff can set things up and have a good nights' sleep instead of getting up at Way Freaking Early O'clock to make changes outside of normal office hours.
tinydns implements this more or less natively via automatic TTL adjustment of a record formatted to indicate an expiry time, and automatic publication of a record with a starting time.
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Milestone: | → 1.4 |
---|
comment:3 by , 11 years ago
Milestone: | 1.4 → 1.2 |
---|
comment:4 by , 11 years ago
(In [543]) /trunk
Implement most of the UI and back end for handling scheduled changes
to records. See #40.
This turned out to be most of what I had vaguely imagined; only SOA
records can't sanely be set for scheduled changes yet (can't think of
a scenario where this would even be useful) and there's only a small
dusting of UI chrome left for another time.
Bumped up from projected 1.4 to 1.2 per request from Reid Sutherland.
(In [367]) /trunk