NOTE: THIS IS FOR HISTORICAL REFERENCE ONLY. Project moved to Percipia repo
- CSV file - headers are representative of fields in configuration file
- Dummy configuration file - file to be loaded into memory and altered to suit
- JSON file containing parameters. See bleow for detail.
- Name of output directory (to be located in project directory), supplied at runtime.
- Name of copy directory (should we copy to tftpboot? ultimately that is the question), supplied at run time
- textOrXML - tell program if text based or xml based string replacement
- text_delimiter - if text file, tell program to separate keys and vals based on this parameter.
- text_delimiter_override - Some config files do not have merely empty values, Bittel for instance outputs a file with parameters that are not delimited AND have no value. The override signifies: IF delimiter does not exist, THEN add delimiter and value to key.
- configfile_extension - extension used to find the config file and write out new config files. MUST contain a period as first character.
- filename_field - name of the field which contains detail to name the file, USUALLY mac address related
- filename_to_upper_bool - true or false, should letters in filename be capitalize?
- filename_prefix_or_none - some config files need a prefix, for example "SEP" for cisco.
{
"textOrXML": "XML",
"text_delimiter": "\t",
"text_delimiter_override": "true",
"filename_extension": ".xml",
"filename_field": "MAC_ADDRESS",
"filename_to_upper_bool": "true",
"filename_prefix_or_none": "SEP"
}
- Files named with MAC address, containing appropriate configuration
- Add option to script to create a mock csv input file with appropriate csv headers