Python tool for exporting/importing a policy package or parts of it

[J__Bendonis]

The scripts seemed to work well in exporting the package, but on the import, it imports all the objects, but the rulebase comes up as a single line for me.  (Excluding the any/any drop).

I'm trying to move a policy package from one management server to another (consolidation of management). 

The original policy is about ~130 lines long for reference.  Even importing into a fresh R80 management station, it doesn't seem to work successfully.

Any suggestions?

[J__Bendonis]

It looks like there is a bug in how it created the csv for the rules import: 

/snip

Adding access rules to layer 'New_Standard Security'...
Error occured during parsing of CSV file.
Line 7 column 40: Unexpected character in csv file. String value is not followed by double-quotes
Failed to read parameters file [01__add-access-rule__2017_07_27_09_43.csv]: Invalid format

code: "generic_err_invalid_parameter"
message: "Invalid parameter for [position]. The invalid value [73] should be replaced by one of the following values: [1-2]"

Adding access sections to layer 'New_Standard Security'...
Line 2: code: "generic_err_invalid_parameter"
message: "Invalid parameter for [position]. The invalid value [14] should be replaced by one of the following values: [1-2]"

Line 3: code: "generic_err_invalid_parameter"
message: "Invalid parameter for [position]. The invalid value [17] should be replaced by one of the following values: [1-2]"

Line 4: code: "generic_err_invalid_parameter"
message: "Invalid parameter for [position]. The invalid value [18] should be replaced by one of the following values: [1-2]"

Line 5: code: "generic_err_invalid_parameter"
message: "Invalid parameter for [position]. The invalid value [22] should be replaced by one of the following values: [1-2]"

Line 6: code: "generic_err_invalid_parameter"
message: "Invalid parameter for [position]. The invalid value [24] should be replaced by one of the following values: [1-2]"

/endsnip

I'm in the process of digging through the export packages currently, but that appears to be the root of the issue.

[Adam_Galmor]

Hello,

A new version of the tool will be uploaded soon (during next week).

Thank you for your patience,

Adam Galmor

[Adam_Galmor]

A new version of the tool, 2.0, has been uploaded.