Delete end-date sunrise, landrush, and sunrush phases

This also deletes the associated commands and domain application specific
entities.

We haven't used any of these TLD phases since early 2015 and have no
intent to do so in the future, so it makes sense to delete them now so we
don't have to carry them through the Registry 3.0 migration.

Note that, while there are data model changes, there should be no required
data migrations. The fields and entities being removed will simply remain
as orphans. I confirmed that the removed types (such as the SUNRUSH_ADD
GracePeriodType) are no longer used in production data, and left types
that are still used, e.g. BillingEvent.Flag.LANDRUSH or
HistoryEntry.Type.ALLOCATE.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=228752843
This commit is contained in:
mcilwain 2019-01-10 12:09:14 -08:00 committed by Ben McIlwain
parent c74ffd7559
commit 580302898d
282 changed files with 344 additions and 17634 deletions

View file

@ -50,11 +50,15 @@ public class HistoryEntry extends ImmutableObject implements Buildable {
CONTACT_TRANSFER_REJECT,
CONTACT_TRANSFER_REQUEST,
CONTACT_UPDATE,
/**
* Used for history entries that were allocated as a result of a domain application.
*
* <p>Domain applications (and thus allocating from an application) no longer exist, but we have
* existing domains in the system that were created via allocation and thus have history entries
* of this type under them, so this is retained for legacy purposes.
*/
@Deprecated
DOMAIN_ALLOCATE,
DOMAIN_APPLICATION_CREATE,
DOMAIN_APPLICATION_DELETE,
DOMAIN_APPLICATION_UPDATE,
DOMAIN_APPLICATION_STATUS_UPDATE,
/**
* Used for domain registration autorenews explicitly logged by
* {@link google.registry.batch.ExpandRecurringBillingEventsAction}.