7 commits

Author	SHA1	Message	Date
mcilwain	8ac8ecf8f6	Rationalize OT&E client ID validation rules ... This makes the validation rules much simpler, thus placing less cognitive load on the users of the console and nomulus tool. The changes are: 1. Don't allow hyphens. No real registrars use hyphens in their client IDs, and it's better to reserve these solely as the delimiter between the base client ID and the number representing the environment. 2. Allow the first character to be a number. This has affected multiple real registrars, causing their OT&E and production client IDs to be different. There's no reason for this restriction, as the only reason motivating it was that there are no TLDs that start with a number. However, the OT&E TLDs are created only in sandbox and never have DNS syncing enabled, so this restriction is purposeless. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=229187198	2019-01-14 16:28:12 -05:00
mcilwain	170980db2f	Statically import commonly used TldState enum values ... Takes advantage of the fact that the default state of a TLD created in tests is GENERAL_AVAILABILITY. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=228916164	2019-01-14 16:23:15 -05:00
guyben	a4fca18657	Set short redemption/add/delete periods for all OT&E TLDs ... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=228791942	2019-01-11 10:59:21 -05:00
mcilwain	580302898d	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	2019-01-10 16:23:35 -05:00
Shicong Huang	a79e254e49	Add an action to check the status of OT&E verification ... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=228333195	2019-01-08 16:46:41 -05:00
jianglai	2e7d71b238	Refactor most of OT&E verification code to exist in utils class ... This does not change existing functionality but will allow us to use this common code in the yet-to-be-created web console action as well. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=227159346	2019-01-02 11:58:36 -05:00
guyben	9d6a7ef66a	Create OT&E entities directly, instead of calling sub-commands ... This is in preparation for having a web-console endpoint to create OTE. In addition - we streamline the code: - we remove support for different premium lists - we remove support for different DNS writers - we never want a "real" DnsWriter for OTE - we remove support of --eap_only, because we don't need it anymore - We use a single password for all the Registrars ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=225841694	2018-12-20 07:46:33 -05:00