New Feature: Record expiration#831
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new field
expiration_dateto the Record model. It can be set to a date when a record should be considered expired and no longer be used in DNS zone deployments.is_expiredthat returnsTrueif a record hasexpiration_dateset and the date in that field is in the past.Recordobjects contains the expiration date and anexpiredfield that becomes true for expired records as defined above.expiration_dateif it is defined, and a "Record is expired" warning when the expiration date is in the past.expiration_date_beforeandexpiration_date_afterfilters or by using the booleanexpiredfilter. The filter form also presents these options.