4 commits

Author	SHA1	Message	Date
gbrodman	d1e3194fce	Don't delete or "redeem" unlimited use AllocationTokens ... We haven't started dealing with timing or discounts yet, but unlimited use tokens should actually be unlimited use ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=243318266	2019-04-15 14:57:02 -04:00
mcilwain	df5d9957f7	Move the AllocationToken entity to the token subpackage ... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=204485366	2018-07-14 01:37:03 -04:00
mcilwain	4d5d1e02a5	Add DateTime as extensibility param for allocation token logic ... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=185002910	2018-02-20 15:27:42 -05:00
mcilwain	9d532cb507	Add extensibility framework for allocation tokens ... This uses an extensibility mechanism similar to that of WhoisCommandFactory and CustomLogicFactory, namely, that a fully qualified Java class is specified in the YAML file for each environment with the allocation token custom logic to be used. By default, this points to a no-op base class that does nothing. Users that wish to add their own allocation token custom logic can simply create a new class that extends AllocationTokenCustomLogic and then configure it in their .yaml config files. This also renames the existing *FlowCustomLogic *Flow instance variables from customLogic to flowCustomLogic, to avoid the potential confusion with the new AllocationTokenCustomLogic class that also now exists. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=183003112	2018-02-01 21:54:29 -05:00

Renamed from java/google/registry/flows/domain/AllocationTokenFlowUtils.java (Browse further)