fix: Implement tracking expiration date for ru/su domains #17
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
TwiN
approved these changes
Sep 20, 2023
TwiN
reviewed
Sep 20, 2023
|
Thank you for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hello. We're transitioning from
.ruto.spacedomains but still need to track expiration for.ruuntil the migration and all the redirects are finished.Summary
Implement domain expration and state tracking for
.ruand.sudomains. These domains use slightly different semantics described in the following doc: linkUnfortunately it's in Russian, so just navigate to page 5 where the names of all the fields are present. They don't specify which format the date field is in, but it seems to be compliant with ISO8601.
Checklist
README.md, if applicable.