Feat(eos_cli_config_gen): Enhance event-handlers model to accommodate other triggers with their specificities.

[Shivani-gslab]

Change Summary

Refactor event-handlers model to accommodate other triggers with their specificities

Related Issue(s)

Fixes #3267

Component(s) name

arista.avd.eos_cli_config_gen

Proposed changes

Adding a dict with extra settings per trigger type.

        trigger: <str; "on-boot" | "on-counters" | "on-intf" | "on-logging" | "on-maintenance" | "on-startup-config" | "vm- 
                      tracer vm">
        trigger_on_counters:

          # Set the counters condition expression.
          condition: <str>

          # Set the granularity of event counting for a wildcarded condition.
          # Example -
          #   condition ( Arad*.IptCrcErrCnt.delta > 100 ) and ( Arad*.UcFifoFullDrop.delta > 100 )
          #   [* wildcard is used here]
          granularity_per_source: <bool>

          # Set the polling interval in seconds.
          poll_interval: <int>
        trigger_on_logging:

          # Set the polling interval in seconds.
          poll_interval: <int>

          # Regular expression to use for searching log messages.
          regex: <str>
        trigger_on_intf:

          # Interface name.
          # Example - Ethernet4
          #           Loopback4-6
          #           Port-channel4,7
          interface: <str; required>

          # Action is triggered upon changes to interface IP address assignment.
          ip: <bool>

          # Action is triggered upon changes to interface ip6 address assignment.
          ip6: <bool>

          # Action is triggered upon changes to interface operStatus.
          operstatus: <bool>

How to test

Checklist

User Checklist

• N/A

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[MaheshGSLAB]

One more thing i noticed that when i do not give action for any trigger then playbook get error on documentation.

TASK [arista.avd.eos_cli_config_gen : Generate device documentation] *********************************************************************
fatal: [leaf1-dc1 -> localhost]: FAILED! => {"msg": "'dict object' has no attribute 'action'. 'dict object' has no attribute 'action'"}

[Shivani-gslab]

One more thing i noticed that when i do not give action for any trigger then playbook get error on documentation.

TASK [arista.avd.eos_cli_config_gen : Generate device documentation] *********************************************************************
fatal: [leaf1-dc1 -> localhost]: FAILED! => {"msg": "'dict object' has no attribute 'action'. 'dict object' has no attribute 'action'"}

Created a separated issue to fix this.

[sugetha24]

LGTM