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
..
files	Add extensibility framework for allocation tokens	2018-02-01 21:54:29 -05:00
BUILD	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
ConfigUtils.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
package-info.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
RdapNoticeDescriptor.java	Format some imports using fix_imports.py	2017-10-24 16:53:47 -04:00
RegistryConfig.java	Add extensibility framework for allocation tokens	2018-02-01 21:54:29 -05:00
RegistryConfigSettings.java	Add extensibility framework for allocation tokens	2018-02-01 21:54:29 -05:00
RegistryEnvironment.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
YamlUtils.java	Rationalize logging statements across codebase	2018-01-19 14:56:45 -05:00