Updated to reflect changes to version, folder structure, and filenames.
The value of ${version} for this document is one of the following:
- Version: v00.60.12 ${version}
- Version: v00.60.12.100 ${version.revision}
This document provides an overview of the file and folder purpose and utilization for the R8X Management API Scripts for Objects and Policy and Layers export, import, set-update, delete, and rename operations, as well as the development environment elements provided.
The approach is to provide a folder by folder overview of provided files and their respective purpose and potential utilization.
With v00.60.08.050 the folder structure was adjusted to facilitate the other project future work with policy and layers and sharing the _templates and_api_subscripts folders as well as tools.
Presumptive folder structure for R8X API Management CLI (mgmt_cli) Template based scripts deployed to GitHub and deployable content is as follows:
- [.dev] named folders are for development operations
- [.wip] named folders are for development operations
| Folder | Folder Purpose |
|---|---|
/...{script_home_folder}/devops[.dev]/ |
the folder containing the script set, generally /var/log/__customer/devops[.dev] |
./_api_subscripts[.wip] |
folder for all scripts |
./_templates[.wip] |
folder for all scripts |
./tools |
folder for all scripts with additional tools not assumed on system |
./objects[.wip] |
folder for objects operations focused scripts |
./objects[.wip]/csv_tools[.wip] |
folder for objects operations for csv handling focused scripts |
./objects[.wip]/export_import[.wip] |
folder for objects operations export, import, set, rename, and delete focused scripts |
./objects[.wip]/export_import_research[.wip] |
folder for objects researching operations export, import, set, rename, and delete focused scripts |
./objects[.wip]/object_operations |
folder for objects operations export, import, set, rename, and delete focused scripts |
./Policy_and_Layers[.wip] |
folder for policy and layers operations focused scripts |
./Session_Cleanup[.wip] |
folder for Session Cleanup operation focused scripts |
./tools.MDSM[.wip] |
folder for Tools focused on MDSM operations scripts |
The devops.dev folder is the root development folder deployed for the scripts package and should be installed somewhere under the /var/log/ folder of the Check Point Gaia host installation. The working default approach for MyBasementCloud is /var/log/__customer/ as that root for /var/log/__customer/devops.dev.
The root of the devops[.dev] folder contains the main documentation and control files for all R8X API development efforts including both Object operations for export, import, set-update, delete, and rename, as well as the Policy and Layers operations for export and import.
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
command_line_parameters.devops.${version.revision}.tsv: this documentation file outlines the different Command Line Interface (CLI) Parameters for the scripts as a Tab Separated Value (.tsv) file.File_and_Folder_Purpose_and_Utilization.${version.revision}.md: this documentation file is the current file being read, describing the purpose and utilization of the files and folders of the project.LIMITATIONS_and_CAVEATS.md: this documentation file lists the current known limitations and caveats for the script packageREADME.md: this documentation file is the primary overview documentation for the scripts project, and is also used on GitHub for the project README.md filesupported_objects.version.tsv.md: this documentation file describes the table columns of the supported_objects.${version.revision}.tsv file for reference.supported_objects.${version.revision}.tsv: this documentation file identifies the supported objects for the Objects operations scripts, and how they are supported for the different operations. Each objects is provide a row in the Tab Separated Value (.tsv) file, and the columns are specific items described or documented.
These files provide information regarding the version of the package of scripts.
Files:
devops_version.${version.revision}.version: Version reference file for this version and revision of the scripts - empty file${version.revision}.${subrevision}.wip.${DATE-TIME-GROUP[YYYY-MM-DD-HHmmZZZ]}.info: Version reference file with version, revision, subrevision, and Date-Time-Group - empty file
The following scripts are in the root of the folder ./devops.dev and will execute a minimu export for import on the local managemnet server (SMS). Other scripts for more detailed operations and testing are located under the ./devops[.dev]/objects[.wip]/object_operations folder.
Script Files:
_minimum_exports.sh: Execute the author's bare minimum export operations to enable import for SMS, Critical Performance Impact (CPI) objects, like all application-sites are not exported._minimum_exports_with_some_do_cpi.sh: Execute the author's bare minimum export operations to enable import for SMS, with some commands utilizing the CLI parameter to execute with Critical Performance Impact (CPI) objects._minimum_system_data_exports_with_some_do_cpi.sh: Execute the author's standard export operations using domain "System Data" for SMS, with some commands utilizing the CLI parameter to execute with Critical Performance Impact (CPI) objects.
These files are used for the actual operations of the scripts and utilized in the deployed environment.
Files:
.environment_info.json: JSON file for configuration/customization of user experience when executing scripts in operational environment, in this case bash on Check Point Gaia host.
These files are used for the development operations of the scripts and utilized in the development environment, but can be utilized in the deployed environment for operations also at a later time.
Files:
solution_info.json: JSON file for configuration/identification of the scripts during operations in the development environment, used by the Windows Command Line (CMD) Development Environment Filessolution_info.devops.dev.${version.revision}.json: Versioned and solution identified copy of the solution_info.json file
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzMakeUpdatesScriptsNow.devops.dev.objects.CMDzzOpenFileTypesInTextFileEditor.devops.dev.objects.bash.CMDzzOpenFileTypesInTextFileEditor.devops.dev.policy_and_layers.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-2parm.devops.dev.objects.CMDzzZRz_Rename_Version-2parm.devops.dev.policy_and_layers.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.devops.dev.objects.CMDzzZTz_Touch.devops.dev.policy_and_layers.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
Template for an new folders created under the existing folder structure with default files and folders stipulated for a new solution or needed folder.
Not provided to GitHub.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.sh.CMD
Folder for logs generated by scripts for the Windows Command Line (CMD) and future PowerShell development scripts.
Not provided to GitHub.
Folder for development operations scripts and templates for change documentation files and developmental strawman content.
Not provided to GitHub.
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzZTz_Touch.CMDzzZTz_Touch.sh.CMD
The folder for tracking changes to the specific operations scripts is the '.../deveops.dev/__Updates' with subfolders for Objects and Policy and Layers operations.
Not provided to GitHub.
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzZTz_Touch.CMDzzZTz_Touch.sh.CMD
Objects operations script changes are documented in this folder in specific subfolders based on the detail version and date of the changes made.
Policy and Layers operations script changes are documented in this folder in specific subfolders based on the detail version and date of the changes made.
The development environment Windows Command Line scripts specific to '.../devops.dev' are stored and developed in this folder, which is also the root target for distribution of common Windows Command Line scripts in the MyBasementCloud environment.
Not provided to GitHub.
These files are used for the development operations of the scripts and utilized in the development environment, but can be utilized in the deployed environment for operations also at a later time.
Files:
solution_info.json: JSON file for configuration/identification of the scripts during operations in the development environment, used by the Windows Command Line (CMD) Development Environment Files. Specific to the scripting for Windows Command Line in the '.../deveops.dev/__Windows.CMD' foldersolution_info.${CMD_version.CMD_revision}.json: Version copy ofsolution_info.json
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files local to the devops.dev environment managed here:
__deploy_current_CMD_files.devops.dev.CMD: Script to deploy the Windows Command Line scripts to their utilization and backuup folders__deploy_current_CMD_files.devops.dev.${CMD_version.CMD_revision}.CMD: Versioned copy of '__deploy_current_CMD_files.devops.dev.CMD file'__MakeFixesScriptsNow.devops.dev.Windows.CMD.CMD: Script to create the files to document changes for the Windows Command Line scripts during the development process__MakeFixesScriptsNow.devops.dev.Windows.CMD.${CMD_version.CMD_revision}.CMD: Versioned copy of '__MakeFixesScriptsNow.devops.dev.Windows.CMD.${CMD_version.CMD_revision}.CMD'_fixes_updates_info.TBEx.devops.dev._Windows.CMD.${DATE_YYYY-MM-DD}.${CMD_version.CMD_revision}.original.CMD: File documenting original content revised by script update_fixes_updates_info.TBEx.devops.dev._Windows.CMD.${DATE_YYYY-MM-DD}.${CMD_version.CMD_revision}.updated.CMD: File documenting changed content revised by script updatezzMakeUpdatesScriptsNow.devops.dev.objects.CMD: Script to create the files used to document changes for the bash scripts for devops.dev Objects operations during the development processzzMakeUpdatesScriptsNow.devops.dev.objects.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzMakeUpdatesScriptsNow.devops.dev.objects.CMD'zzMakeUpdatesScriptsNow.devops.dev.policy_and_layers.CMD: Script to create the files used to document changes for the bash scripts for devops.dev Policy and Layers operations during the development processzzMakeUpdatesScriptsNow.devops.dev.policy_and_layers.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzMakeUpdatesScriptsNow.devops.dev.policy_and_layers.CMD'- zzOpenFileTypesInTextFileEditor.devops.dev.objects.bash.CMD : Script to open devops.dev Objects operations bash scripts in Windows Text Editor pulling from specific folders
zzOpenFileTypesInTextFileEditor.devops.dev.objects.bash.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzOpenFileTypesInTextFileEditor.devops.dev.objects.bash.CMD'zzOpenFileTypesInTextFileEditor.devops.dev.policy_and_layers.bash.CMD: Script to open devops.dev Policy and Layers operations bash scripts in Windows Text Editor pulling from specific folderszzOpenFileTypesInTextFileEditor.devops.dev.policy_and_layers.bash.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzOpenFileTypesInTextFileEditor.devops.dev.policy_and_layers.bash.CMD'zzZRz_Rename_Version-2parm.devops.dev.objects.CMD: Script that executes a rename utilizing two parameters "old version" and "new version" on the files in the devops.dev Objects operations scripts folderszzZRz_Rename_Version-2parm.devops.dev.objects.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzZRz_Rename_Version-2parm.devops.dev.objects.CMD'zzZRz_Rename_Version-2parm.devops.dev.policy_and_layers.CMD: Script that executes a rename utilizing two parameters "old version" and "new version" on the files in the devops.dev Policy and Layers operations scripts folderszzZRz_Rename_Version-2parm.devops.dev.policy_and_layers.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzZRz_Rename_Version-2parm.devops.dev.policy_and_layers.CMD'zzZTz_Touch.devops.dev.objects.CMD: Script to execute a Unix touch operation on all the files associated with the devop.dev Objects operations scriptszzZTz_Touch.devops.dev.objects.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzZTz_Touch.devops.dev.objects.CMD'zzZTz_Touch.devops.dev.policy_and_layers.CMD: Script to execute a Unix touch operation on all the files associated with the devop.dev Policy and Layers operations scriptszzZTz_Touch.devops.dev.policy_and_layers.${CMD_version.CMD_revision}.CMD: Versioned copy of 'zzZTz_Touch.devops.dev.policy_and_layers.CMD'
Windows Command Line script Files common to MyBasementCloud script development operations managed elsewhere:
WINTOUCH.CMD: Script to execute Windows equivalent of Unix touch operationzzOpenFileTypesInTextFileEditor.versions.CMD: Script to open version related files in Windows Text Editor pulling from folder and all subfolderszzOpenFileTypesInTextFileEditor.Windows_CMD.CMD: Script to open Windows CMD files in Windows Text Editor pulling from folder and all subfolderszzOpenFileTypesInTextFileEditor.Windows_CMD.CMD_Tools.CMD: Script to open Windows CMD files in Windows Text Editor pulling from folder in a script development CMD file specific orderzzZCz_Clear__historyFolders.CMD: Script to clear and remove the hidden __history folders from this folder and all subfolders, created by the text editorzzZRz_Rename_Version-3parm.CMD: Script that executes a rename utilizing three parameters "old version", "new version", and "starting folder path" on the files in the "starting folder path" folder and sub-folderszzZRz_Rename_Version.CMD: Script that executes a rename utilizing two parameters "old version" and "new version"on the files in the current folderzzZRz_Rename_Version_Recursive.CMD: Script that executes a rename utilizing two parameters "old version" and "new version"on the files in the current folder and all sub-folderszzZSz_Create_Shortcuts_in_Current_Folder.CMD: Creates Windows shortcuts files for all files in the current folderzzZSz_Create_Shortcuts_in_Parent_Folder.CMD: Creates Windows shortcuts files for all files in the parent folder of the current folderzzZTz_Lock.CMD: Executes a lock operation on all files, setting them to read-onlyzzZTz_Touch.CMD: Executes Unix touch command on all fileszzZTz_Touch.sh.CMD: Executes Unix touch command on all bash .sh fileszzZTz_TouchLock.CMD: Executes a Unix touch command and then locok (set to read-only) on all fileszzZTz_Unlock.CMD: Executes an unlock operation on all files, setting them to read-writezzZTz_UnlockTouch.CMD: Executes and unlock operation (set to read-write) followed by a Unix touch operation on all fileszzZTz_UnlockTouchReLock.CMD: Executes and unlock operation (set to read-write) followed by a Unix touch operation on all files followed by a lock operation on all files, setting them to read-only
To simplify script development and operations, common operations are collected into subscripts, in this case with the Check Point Management REST API operations focus, thus API subscripts. These subscripts are utilized by scripts that leverage the script templates in the .../devops.dev/_templates[.wip] folder, like those under ../objects[.wip]
These files provide information regarding the version of the package of scripts.
Files:
api_subscripts_version.${functional_level}.${version}.version: Version file identifying the API subscriptsversion.api_subscripts.${version.revision}.version: Version file identifying the API subscripts, used for alternative method from first
Script Files:
basic_script_setup_API_scripts.subscript.common.${functional_level}.${version}.sh: Subscript to handle basic setup of the bash script for Check Point Management API operationscmd_line_parameters_handler.subscript.common.${functional_level}.${version}.sh: Subscript to handle Command Line Parameters, parsing the script primary call for parameters and evaluating the information. Also provides associated specific Command Line Parameter based help.identify_gaia_and_installation.subscript.common.${functional_level}.${version}.sh: Subscript with Check Point Gaia host specific scripting to identify installed version and installation type specifics.mgmt_cli_api_operations.subscript.common.${functional_level}.${version}.sh: Subscript for handling common operations for the Check Point Management REST API operated in bash via mgmt_cli calls.script_output_paths_and_folders_API_scripts.subscript.common.${functional_level}.${version}.sh: Subscript that handles configuration of variables for script operational common file paths and folder locations including creating of missing folders for the Check Point Management API scripts. This subscript also includes the handling for nohup operations initiated by a "do_script_nohup[.sh]" call as defined by the 'bash 4 Check Point' scripts that are standard implementation for MyBasementCloud operations.
Template files for scripts specific to this folder and/or operation.
Script Template Files:
api_mgmt_cli_shell_template_common_subscripts_handler.template.subscript.common.${functional_level}.${version}.sh: Template script file for subscript type script files with specific validations to ensure versioning fidelity.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
Code Snippets are segments of script code for copy-pasting into scripts to perform a specific set of operations. The '_code_snippets' folder for the '_api_subscripts' provides the Code Snippets for the specific API Subscripts, to utilize them in other scripts.
Script Files:
code_snippet.basic_script_setup_API_scripts.common.${functional_level}.${version}.sh: Code Snippets for implementation utilization of thebasic_script_setup_API_scripts.subscript.common.${functional_level}.${version}.shscriptcode_snippet.cmd_line_parameters_handler.common.${functional_level}.${version}.sh: Code Snippets for implementation utilization of thecmd_line_parameters_handler.subscript.common.${functional_level}.${version}.shscriptcode_snippet.identify_gaia_and Installation.common.${functional_level}.${version}.sh: Code Snippets for implementation utilization of theidentify_gaia_and_installation.subscript.common.${functional_level}.${version}.shscriptcode_snippet.mgmt_cli_api_operations.common.${functional_level}.${version}.sh: Code Snippets for implementation utilization of themgmt_cli_api_operations.subscript.common.${functional_level}.${version}.shscriptcode_snippet.script_output_paths_and_folders_API_scripts.common.${functional_level}.${version}.sh: Code Snippets for implementation utilization of thescript_output_paths_and_folders_API_scripts.subscript.common.${functional_level}.${version}.shscript
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzTouch.sh.CMD
The '_templates[.wip]' folder contains bash script templates and some rough testing files for generating bash scripts for the devops.dev operations, utilizing the API subscripts in the '../_api_subscripts' folder. Most bash shell [.sh] scripts provided are written utilizing these templates.
These files provide information regarding the version of the package of scripts.
Files:
_templates_version.${version.revision}.version: Version file for the script templates provided
These files are used for the actual operations of the scripts and utilized in the deployed environment.
Files:
.environment_info.json: JSON file with environmental controls as an example and for use with the provided bash script templates.
Template files for scripts specific to this folder and/or operation. These templates are fully functional scripts missing the desired operational content for the final script, but are able to demonstrate operations with the API subscripts
Script Template Files:
api_mgmt_cli_shell_template_action_handler.template.${version}.sh: Template for generating an action handler subscript.api_mgmt_cli_shell_template_with_cmd_line_parameters.template.${version}.sh: Template for generating a script that utilizes Command Line Paramenters, but handles those parameters in the main script, not via the common Command Line Paramenter handler API subscript 'cmd_line_parameters_handler.subscript.common.${functional_level}.${version}.sh'. Includes Check Point Management API handling for login, operatin (defined by script developer), publish, policy installation if needed [future], and logout operations.api_mgmt_cli_shell_template_with_cmd_line_parameters_script.template.${version}.sh: Template for generating a script that utilizes Command Line Paramenters, via the common Command Line Paramenter handler API subscript 'cmd_line_parameters_handler.subscript.common.${functional_level}.${version}.sh'. Includes Check Point Management API handling for login, operatin (defined by script developer), publish, policy installation if needed [future], and logout operations.
Script Files:
test._script.environment_info_json.${version}.sh: Test script to evaluate operation of the JSON file '.environment_info.json', for configuring local environmental and display parameters.test._templates.${version}.sh: Test script for executing tests against the 'api_mgmt_cli_shell_template_with_cmd_line_parameters_script.template.${version}.sh' template.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
Default output folder for bash scripts if not specifically changed or referenced.
Folder for research and reference materials used in the script template development process.
Files:
reference.jq_queries_and_output_formating.bash: research referece file for JQ and JSON operations
Tools distribution folder to include expected tools utilization by the '.../devops.dev' scripts operations.
Folder with the current JSON Query, version 1.6, binaries from GitHub for distribution with distribution files. Distribution content is in the '../GitHub' subfolder.
Current JSON Query version: 01.06.2018-11.01
Tools repository folder for deployable Windows Command Line (CMD) and PowerShell [Future] files for deployment distribution.
Not provided to GitHub.
Scripts for the Management API Objects operations for export, import, set-update, delete, and rename, as well as CSV file management scripts are located here. The main folders below break out the operations for CSV file management version Objects operations.
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
These files provide information regarding the version of the package of scripts.
Files:
csv_tools_version.${version.revision}.version: Current version details for the '../csv_tools.wip' scripts
Script Files:
api_add_csv_error_handling_to_csv_file.sh: Raw script to handle processing of a single file, passed as command line parameter to modify with CSV error handling columns.api_subpend_csv_error_handling_to_object_csv_files.sh: Script that processes all CSV files in a provided folder for addition of CSV error handling columns, supports standard command line parameter processing.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
export_import.wip folder is for scripts executing the actual export, import, set-update, delete, and rename operations, as well as scripts that execute a set of these operations for complete processes, like testing, or common exports. The folder also includes default locations for output and where operational files could be found for certain operations, like testing, import, or delete, and a default dump output folder.
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
supported_objects.WIP.${version.revision}.tsv: This documentation file identifies the supported objects for the Objects operations scripts as a Work-In-Progress (WIP), and how they are supported for the different operations. Each objects is provide a row in the Tab Separated Value (.tsv) file, and the columns are specific items described or documented..testing_operations_MDSM.${version.revision}.sh: Testing Operations scripts with command line parameters to execute testing against MDSM..testing_operations_SMS.${version.revision}.sh: Testing Operations scripts with command line parameters to execute testing against SMS..testing_schema_MDSM.${version.revision}.sh: Schema of scripts with command line parameters to execute testing against MDSM..testing_schema_SMS.${version.revision}.sh: Schema of scripts with command line parameters to execute testing against SMS.
These files provide information regarding the version of the package of scripts.
Files:
export_import_version.${version.revision}.version: Current version of the '../export_import.wip' script files
Script Files:
cli_api_delete_objects_using_csv.sh: Script to delete objects on target SMS or MDSM Domain using CSV files in supported format, controlled by Command Line Parameters. All CSV files are expected in the same source folder.
Script Files:
cli_api_actions.export_objects_to_csv.sh: Action handler for object export to CSV format, utilized by other scripts.cli_api_actions.export_objects_to_json.sh: Action handler for object export to JSON format, utilized by other scripts. Also populates the JSON Repository.cli_api_export_all_domains_objects.sh: Script to handle looping through all MDSM domains on a target MDSM MDS exporting all objects in JSON and CSV format controlled by Command Line Parameters, also populating the JSON repository.cli_api_export_all_domains_objects_to_csv.sh: Script to handle looping through all MDSM domains on a target MDSM MDS exporting all objects in CSV format controlled by Command Line Parameters.cli_api_export_objects.sh: Script to handle exporting all objects on an SMS or for a specific MDSM Domain in JSON and CSV format controlled by Command Line Parameters, also populating the JSON repository.cli_api_export_objects_to_csv.sh: Script to handle exporting all objects on an SMS or for a specific MDSM Domain in CSV format controlled by Command Line Parameters.cli_api_export_objects_to_csv.testing.msdm.sh: Script to handle subset of objects export, based on in script changes to active or commented out object actions, for CSV format, to assist in testing and developing complete and/or working exports for objects, on MDSM MDS target host.cli_api_export_objects_to_csv.testing.sh: Script to handle subset of objects export, based on in script changes to active or commented out object actions, for CSV format, to assist in testing and developing complete and/or working exports for objects, on SMS target host.
Script Files:
cli_api_import_objects_from_csv.sh: Script to import objects to target SMS or MDSM Domain using CSV files in supported format, controlled by Command Line Parameters. All CSV files are expected in the same source folder.
Script Files:
cli_api_rename_to_new_name_objects_from_csv.sh: Script to rename objects on target SMS or MDSM Domain using CSV files in supported format, controlled by Command Line Parameters. All CSV files are expected in the same source folder.
Script Files:
cli_api_set_update_objects_from_csv.sh: Script to set or update objects on target SMS or MDSM Domain using CSV files in supported format, controlled by Command Line Parameters. All CSV files are expected in the same source folder.
Script Files:
500plus_objects_to_single_json_in_dump.lite.sh: Process all instances of a type of object provided as a Command Line Parameter into a single JSON output file.
Script Files:
wip.object_export_testing.sh: Script to handle specific objects export, based on in script changes to active or commented out object actions, for CSV format, to assist in testing and developing complete and/or working exports for objects, on SMS target host.
JSON Files:
- None
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
Location for scripts deprecated since last version release, may not be present.
Default folder for expected files during Object delete operations.
Default folder for output files during Object operations.
Default folder for expected files during Object import operations.
Example CSV files and instructions to test the objects operations processes.
Files:
testing_operations_multi_domain_regular.txt: sample instructions for execution in MDSM environmenttesting_operations_single_management_regular.txt: sample instructions for execution in SMS environment
Example CSV files to test deleting objects process.
Files:
address-ranges_name_csv.csvdns-domains_name_csv.csvgroups-with-exclusion_name_csv.csvgroups_name_csv.csvhosts_name_csv.csvnetworks_name_csv.csvsecurity-zones_name_csv.csv
Example CSV files to test deleting with a large number of objects process.
Files:
address-ranges_name_csv.csvdns-domains_name_csv.csvgroups-with-exclusion_name_csv.csvgroups_name_csv.csvhosts_name_csv.csvnetworks_name_csv.csvsecurity-zones_name_csv.csv
Example CSV files to test the import objects process.
Files:
address-ranges_full_csv.csvdns-domains_full_csv.csvgroup-members_full_csv.csvgroups-with-exclusion_full_csv.csvgroups_full_csv.csvhost-interfaces_full_csv.csvhosts_full_csv.csvnetworks_full_csv.csvsecurity-zones_full_csv.csv
Example CSV files to test the import with a large number of objects process.
Files:
address-ranges_full_csv.csvdns-domains_full_csv.csvgroup-members_full_csv.csvgroups-with-exclusion_full_csv.csvgroups_full_csv.csvhost-interfaces_full_csv.csvhosts_full_csv.csvnetworks_full_csv.csvsecurity-zones_full_csv.csv
Example CSV files to test the set-update process.
Files:
groups_full_csv.csvhosts_full_csv.csvnetworks_full_csv.csvsecurity-zones_full_csv.csv
export_import_research[.wip] folder is for research for scripts executing the actual export, import, set-update, delete, and rename operations, as well as scripts that execute a set of these operations for complete processes, like testing, or common exports.
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
- NONE
These files provide information regarding the version of the package of scripts.
Files:
export_import_research_version.${version.revision}.version: Current version of the '../export_import_research.wip' script files
Script Files:
wip.test_read_exobdef_json_file.sh: Script to test the operations for reading JSON Object Export Definition Files, for development of JSON controlled operations on objects.
JSON Files:
export_objects_definition.json: JSON Object Export Definition file for operational implementation.export_objects_definition.template.json: JSON Object Export Definition file template for operational implementation.export_objects_definition.test.json: JSON Object Export Definition file for testing implementation.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
The 'object_operations' folder provides operations scripts that execute a process utilizing the scripts in the './export_import[.wip]' and './csv_tools[.wip]' folders.
These files provide information regarding the version of the package of scripts.
Files:
object_operations_version.${version.revision}.version: Current version details for the '../object_operations' scripts
Script Files:
_standard_exports_with_some_do_cpi.sh: Execute the author's standard export operations with all objects (-SO) and Non-System Objects (NSO) for SMS, with some commands utilizing the CLI parameter to execute with Critical Performance Impact (CPI) objects._standard_system_data_exports_with_some_do_cpi.sh: Execute the author's standard export operations using domain "System Data" with all objects (-SO) for SMS, with some commands utilizing the CLI parameter to execute with Critical Performance Impact (CPI) objects.common_csv_exports.sh: Execute the common standard export to CSV with all objects (-SO) and Non-System Objects (NSO) for SMS.common_csv_exports_mdsm.sh: Execute the common standard export to CSV with all objects (-SO) and Non-System Objects (NSO) for MDSM.common_exports.sh: Execute the common standard export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for SMS.common_exports_mdsm.sh: Execute the common standard export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for MDSM.other_main_exports.sh: Execute the other main export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for SMS.other_main_exports_mdsm.sh: Execute the other main export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for MDSM.refresh_all_json_object_repositories.sh: Execute scripts to refresh all JSON Respositories for an SMS, including all objects (-SO), Non-System Objects (-NSO), and Only System Objecs (-OSO).refresh_all_json_object_repositories_mdsm.sh: Execute scripts to refresh all JSON Respositories for an MDSM MDS, including all objects (-SO), Non-System Objects (-NSO), and Only System Objecs (-OSO).refresh_json_object_repository.sh: Execute scripts to refresh JSON Respository for an SMS, only for the all objects (-SO) repository.refresh_json_object_repository_mdsm.sh: Execute scripts to refresh JSON Respository for an MDSM MDS, only for the all objects (-SO) repository.
Script Files:
test_exports.sh: Execute complete set of scripts to test the export operations scripts, with output of JSON and CSV files, including building all JSON Repositories, for SMS.test_exports_csv.sh: Execute subset set of scripts to test the export operations scripts, with output of CSV files, utilizing JSON Repositories, for SMS.test_exports_csv_mdsm.sh: Execute subset set of scripts to test the export operations scripts, with output of CSV files, utilizing JSON Repositories, for MDSM.test_exports_json.sh: Execute subset set of scripts to test the export operations scripts, with output of JSON files, including building all JSON Repositories, for SMS.test_exports_json_mdsm.sh: Execute subset set of scripts to test the export operations scripts, with output of JSON files, including building all JSON Repositories, for MDSM.test_exports_mdsm.sh: Execute complete set of scripts to test the export operations scripts, with output of JSON and CSV files, including building all JSON Repositories, for MDSM.test_exports_with_some_do_cpi.sh: Execute complete set of scripts to test the export operations scripts, with output of JSON and CSV files, including building all JSON Repositories, for SMS, with some commands utilizing the CLI parameter to execute with Critical Performance Impact (CPI) objects.test_import_export_set_update_delete.sh: Execute a series scripts to test import, export, set_update, export, delete, and export to review all key functions of the scripts.test_import_export_set_update_delete_mdsm.sh: Execute a series scripts to test import, export, set_update, export, delete, and export to review all key functions of the scripts against the MDSM domain.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
The 'do_cpi' folder provides operations scripts that execute a process utilizing the scripts in the './export_import[.wip]' and './csv_tools[.wip]' folders with additional CLI parameters to execute operations to include Critical Performance Impacting (CPI) objects.
Script Files:
common_csv_exports_do_cpi.sh: Execute the common standard export to CSV with all objects (-SO) and Non-System Objects (NSO) for SMS. objects versus the default 250.common_exports_do_cpi.sh: Execute the common standard export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for SMS.other_main_exports_do_cpi.sh: Execute the other main export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for SMS.refresh_all_json_object_repositories_do_cpi.sh: Execute scripts to refresh all JSON Respositories for an SMS, including all objects (-SO), Non-System Objects (-NSO), and Only System Objecs (-OSO).refresh_json_object_repository_do_cpi.sh: Execute scripts to refresh JSON Respository for an SMS, only for the all objects (-SO) repository.
Script Files:
test_exports_do_cpi.sh: Execute complete set of scripts to test the export operations scripts, with output of JSON and CSV files, including building all JSON Repositories, for SMS.test_exports_csv_do_cpi.sh: Execute subset set of scripts to test the export operations scripts, with output of CSV files, utilizing JSON Repositories, for SMS.test_exports_json_do_cpi.sh: Execute subset set of scripts to test the export operations scripts, with output of JSON files, including building all JSON Repositories, for SMS.
The 'mdsm_100_max_limit' folder provides operations scripts that execute a process utilizing the scripts in the './export_import[.wip]' and './csv_tools[.wip]' folders with additional CLI parameters to execute operations limiting activity to 100 objects per call.
Script Files:
common_csv_exports_mdsm_100_max_limit.sh: Execute the common standard export to CSV with all objects (-SO) and Non-System Objects (NSO) for MDSM, but with a maximum limit set at 100common_exports_mdsm_100_max_limit.sh: Execute the common standard export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for MDSM, but with a maximum limit set at 100 objects versus the default 250.other_main_exports_mdsm_100_max_limit.sh: Execute the other main export to JSON and CSV, populating the JSON repository with all objects (-SO) and Non-System Objects (NSO) for MDSM, but with a maximum limit set at 100 objects versus the default 250.refresh_all_json_object_repositories_mdsm_100_max_limit.sh: Execute scripts to refresh all JSON Respositories for an MDSM MDS, but with a maximum limit set at 100 objects versus the default 250, including all objects (-SO), Non-System Objects (-NSO), and Only System Objecs (-OSO).refresh_json_object_repository_mdsm_mdsm_100_max_limit.sh: Execute scripts to refresh JSON Respository for an MDSM MDS, but with a maximum limit set at 100 objects versus the default 250, only for the all objects (-SO) repository.
Script Files:
test_exports_csv_mdsm_100_max_limi.sh: Execute subset set of scripts to test the export operations scripts, with output of CSV files, utilizing JSON Repositories, for MDSM, but with a maximum limit set at 100 objects versus the default 250.test_exports_json_mdsm_100_max_limi.sh: Execute subset set of scripts to test the export operations scripts, with output of JSON files, including building all JSON Repositories, for MDSM, but with a maximum limit set at 100 objects versus the default 250.test_exports_mdsm_100_max_limit.sh: Execute complete set of scripts to test the export operations scripts, with output of JSON and CSV files, including building all JSON Repositories, for MDSM, but with a maximum limit set at 100 objects versus the default 250.test_import_export_set_update_delete_mdsm_100_max_limit.sh: Execute a series scripts to test import, export, set_update, export, delete, and export to review all key functions of the scripts against the MDSM domain, but with a maximum limit set at 100 objects versus the default 250.
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
CAVEATS_AND_LIMITATIONS.mdLICENSEREADME.md
These files provide information regarding the version of the package of scripts.
Files:
devops_policy_and_layers_version.v00.00.09.000.versionv00.00.09.000.wip.2021-06-22-1800CDT.info
These files are used for the development operations of the scripts and utilized in the development environment, but can be utilized in the deployed environment for operations also at a later time.
Files:
solution_info.devops.dev.policy_and_layers.v00.00.09.000.jsonsolution_info.json
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzMakeUpdatesScriptsNow.devops.dev.policy_and_layers.CMDzzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.devops.dev.policy_and_layers.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-2parm.devops.dev.policy_and_layers.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.devops.dev.policy_and_layers.CMDzzZTz_Touch.sh.CMD
Files:
https-inspection-rule-detail.example.jsonthreat-prevention-profile-detail.example.jsonthreat-prevention-rule-detail.example.json
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
CAVEATS_AND_LIMITATIONS_Access_Control_Policy.mdREADME.md
Script Files:
list_layer_names.access-layers-from-package.v00.00.09.shlist_layer_names.access-layers.v00.00.09.sh
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
CAVEATS_AND_LIMITATIONS_HTTPS_Inspection_Policy.mdREADME.md
Script Files:
export_to_csv_https_inspection_rule_base.v00.00.09.shimport_from_csv_https_inspection_rule_base.v00.00.09.shlist_layer_names.https-layers-from-package.v00.00.09.shlist_layer_names.https-layers.v00.00.09.sh
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
CAVEATS_AND_LIMITATIONS_Threat_Prevention_Policy.mdREADME.md
Script Files:
export_to_csv_threat_prevention_global_exceptions.v00.00.09.shexport_to_csv_threat_prevention_profiles.export_only.v00.00.09.shexport_to_csv_threat_prevention_profiles.v00.00.09.shexport_to_csv_threat_prevention_rule_base.v00.00.09.shimport_from_csv_threat_prevention_global_exceptions.v00.00.09.wip.shimport_from_csv_threat_prevention_profiles.v00.00.09.wip.shimport_from_csv_threat_prevention_rule_base.v00.00.09.wip.shlist_layer_names.threat-layers-from-package.v00.00.09.shlist_layer_names.threat-layers.v00.00.09.sh
The Session Cleanup scripts are used to handle situation when there are too many API sessions open on the target management host and those sessions that are expired need to be removed.
These files provide information regarding the version of the package of scripts.
Files:
Session_Cleanup_version.${B4CP_version.revision}.template.${version.revision}.version: Version details for the Session Cleanup files
Script Files:
remove_zerolocks_sessions.${version}: Remove all user's sessions that are expired and have Zero locks.remove_zerolocks_web_api_sessions.${version}: Remove all web_api user's sessions that are expired and have Zero locks.show_zerolocks_sessions.${version}: Show all user's sessions that are expired and have Zero locks.show_zerolocks_web_api_sessions.${version}: Show all web_api user's sessions that are expired and have Zero locks.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
The .../tools.MDSM[.wip] folder provides tools to provide supporting operations for working with Check Point Multi-Domain Security Management (MDSM) management hosts Multi-Domain Servers (MDS)
Script Files:
MDM_Get_Domains_List.${version}.sh: Script to output the current list of MDSM Domains on the management host, with Command Line Parameter support for authenticationshow_domains_api.${version}.sh: Script to output the current list of the local management hosts MDSM Domains, stipulating ability to authenticate locally with '-r true' and operating on the actual Multi-Domain Server (MDS) directly.
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
zzOpenFileTypesInTextFileEditor.bash.CMDzzOpenFileTypesInTextFileEditor.versions.CMDzzZCz_Clear__historyFolders.CMDzzZRz_Rename_Version-3parm.CMDzzZRz_Rename_Version.CMDzzZRz_Rename_Version_Recursive.CMDzzZTz_Touch.CMDzzZTz_Touch.sh.CMD
The .../deveops[.dev]/zzz_testing[.wip] folder is used for scripting R&D and documenting the results of the research and testing.
Not provided to GitHub.
Documentation related files in formats that support the material presented. Markdown (.md) files are used for text document style files, while Tab Separated Value (.tsv) files are used for table style information.
Files:
- x
These files provide information regarding the version of the package of scripts.
Files:
- x
These files are used for the actual operations of the scripts and utilized in the deployed environment.
Files:
.environment_info.json
These files are used for the development operations of the scripts and utilized in the development environment, but can be utilized in the deployed environment for operations also at a later time.
Files:
- x
Script Files:
- x
Template files for scripts specific to this folder and/or operation.
Script Template Files:
- a
Windows Command Line (CMD) Development Environment Files (not commonly distributed or provided in GitHub)
Script files for use in Windows Command Line (CMD) Development Environment, potentially PowerShell in the future, to handle common operations during the script development process. These Development Environment scripts may be environment specific to both the development technology/environment, as well as the script focus. Intelligent naming is stipulated where plausible. If a __Windows.CMD folder exists, then the details of the script file purposes is explained there.
Windows Command Line script Files:
- x
Files:
- x
Not provided to GitHub.