Support disable logging console

Enhancement summary

Support deactivating console logging on logging settings

Which component of AVD is impacted

eos_cli_config_gen

Use case example

Need to apply the following commands to a switch:

no logging console

However the logging datamodel does not support this. I am using eos_cli for now, but requesting support for this feature

Describe the solution you would like

Data model update, to look like the following (relevant change on the console settings):

logging:
  console: 
    enable: <true, false | default --> true>
    level:  < severity_level >
  monitor: < severity_level >
  buffered:
    size: < messages_nb (minimum of 10) >
    level: < severity_level >
  trap: < severity_level >
  synchronous:
    level: < severity_level | default --> critical >
  format:
    timestamp: < high-resolution | traditional >
    hostname: < fqdn | ipv4 >
    sequence_numbers: < true | false >
  source_interface: < source_interface_name >
  vrfs:
    < vrf_name >:
      source_interface: < source_interface_name >
      hosts:
        < syslog_server_1 >:
          protocol: < tcp | udp (default udp) >
          ports:
            - < custom_port_1 >
            - < custom_port_2 >
        < syslog_server_2 >:
          ports:
            - < custom_port_1 >
  policy:
    match:
      match_lists:
        < match_list >:
          action: < discard >

Describe alternatives you have considered

using eos_cli

Additional context

No response

Contributing Guide

• I agree to follow this project’s Code of Conduct

[ccsnw]

Valid input under the level key are the syslog severity levels. “none” is not part of them and “disabled” also isn’t.

In order to avoid collision with the “None” keyword we should use “disabled” as Claus explained

[gusmb]

Alternative could be to look at the value of level, and if it is disabled then we disable with no logging xxx (Edited to avoid the “none” word)

Is logging none a valid eos input? If that’s the case, probably not ideal to masquerade it to sth different as there might be a case where someone wants logging none explicitly declared?