|
At this point forge create whole different module for different backeds (leases, reservations etc) that creates config files (set of commands) during each individual step of a test. That makes it hard to maintain - every backend has it's own storage, functions to run/upload. New approach (mostly done but not finished yet) is to create class with configuration and module for each backed would use the same class - but different steps to create config files (xml, json, commands)
|
|
At this point forge create whole different module for different backends (leases, reservations etc) that creates config files (set of commands) during each individual step of a test. That makes it hard to maintain - every backend has it's own storage, functions to run/upload. New approach (mostly done but not finished yet) is to create class with configuration and module for each backed would use the same class - but different steps to create config files (xml, json, commands)
|