print abstract policy to log

[ShiriMoran]

No description provided.

[adisos]

looks good.

maybe for a separate issue, ran with pkg/collector/data/json/Example1.json and got log messages that are not clear:

 INFO        Expression must not be nil and must be of size at least 1

the abstract model is printed this way:

INFO        abstract model
~~~~~~~~~~~~~~
category: Application
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
symbolic inbound rules:
        0. action: allow paths: src: (group = frontend) dst: (group = backend) conn: TCP dst-ports: 445
        1. action: deny paths: src: (*) dst: (*) conn: All Connections
symbolic outbound rules:
        0. action: allow paths: src: (group = frontend) dst: (group = backend) conn: TCP dst-ports: 445
        1. action: deny paths: src: (*) dst: (*) conn: All Connections

another comment, maybe for a separate issue - consider printing in table format (similar to connectivity output, input rules of DFW, etc... there is a func in common pkg to use that - GenerateTableString).

[ShiriMoran]

stract model

please op

looks good.

maybe for a separate issue, ran with pkg/collector/data/json/Example1.json and got log messages that are not clear:

 INFO        Expression must not be nil and must be of size at least 1

the abstract model is printed this way:

INFO        abstract model
~~~~~~~~~~~~~~
category: Application
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
symbolic inbound rules:
        0. action: allow paths: src: (group = frontend) dst: (group = backend) conn: TCP dst-ports: 445
        1. action: deny paths: src: (*) dst: (*) conn: All Connections
symbolic outbound rules:
        0. action: allow paths: src: (group = frontend) dst: (group = backend) conn: TCP dst-ports: 445
        1. action: deny paths: src: (*) dst: (*) conn: All Connections

another comment, maybe for a separate issue - consider printing in table format (similar to connectivity output, input rules of DFW, etc... there is a func in common pkg to use that - GenerateTableString).

Please open a separate issue for the table

[adisos]

Please open a separate issue for the table

do you want to fix the issue about the unclear log message in this PR? (already opened an issue about other unclear log messages).

[ShiriMoran]

Please open a separate issue for the table

do you want to fix the issue about the unclear log message in this PR? (already opened an issue about other unclear log messages).

fixed (" INFO Expression must not be nil and must be of size at least 1" rewritten)

[adisos]

Please open a separate issue for the table

do you want to fix the issue about the unclear log message in this PR? (already opened an issue about other unclear log messages).

fixed (" INFO Expression must not be nil and must be of size at least 1" rewritten)

getting many duplications of this warning in the log:

2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group frontend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group backend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group backend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group frontend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group backend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group frontend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group frontend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group backend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group backend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group frontend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group backend. Thus using the group for synthesis and ignoring the expression
2025/02/09 15:10:19 INFO        Illegal or nil expression attached to group frontend. Thus using the group for synthesis and ignoring the expression
2

can fix here or open a separate issue to avoid these duplications.

I'm having problem in reproducing it; Lets open another issue.