google-nomulus/java/google/registry/flows/custom/CustomLogicFactory.java
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

69 lines
3.1 KiB
Java

// Copyright 2017 The Nomulus Authors. All Rights Reserved.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
package google.registry.flows.custom;
import google.registry.config.RegistryConfig.ConfigModule;
import google.registry.flows.FlowMetadata;
import google.registry.flows.SessionMetadata;
import google.registry.model.eppinput.EppInput;
/**
* A no-op base custom logic factory.
*
* <p>To add custom logic, extend this class, then configure it in
* {@link ConfigModule#provideCustomLogicFactoryClass}. The eppInput and sessionMetadata parameters
* are unused in the base implementation, but are provided so that custom implementations can
* optionally determine how to construct/choose which custom logic class to return. A common use
* case might be parsing TLD for domain-specific flows from the EppInput and then using that to
* choose a different custom logic implementation, or switching based on the registrar
* {@code clientId} in sessionMetadata.
*/
public class CustomLogicFactory {
public DomainCreateFlowCustomLogic forDomainCreateFlow(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainCreateFlowCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
public DomainCheckFlowCustomLogic forDomainCheckFlow(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainCheckFlowCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
public DomainInfoFlowCustomLogic forDomainInfoFlow(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainInfoFlowCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
public DomainUpdateFlowCustomLogic forDomainUpdateFlow(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainUpdateFlowCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
public DomainRenewFlowCustomLogic forDomainRenewFlow(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainRenewFlowCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
public DomainDeleteFlowCustomLogic forDomainDeleteFlow(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainDeleteFlowCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
public DomainPricingCustomLogic forDomainPricing(
EppInput eppInput, SessionMetadata sessionMetadata, FlowMetadata flowMetadata) {
return new DomainPricingCustomLogic(eppInput, sessionMetadata, flowMetadata);
}
}