ancestor: null releases: 0.2.0: changes: breaking_changes: - routeros_facts - allow multiple addresses and neighbors per interface. This makes ``ansible_net_neighbors`` a list instead of a dict (https://github.com/ansible-collections/community.network/pull/6). bugfixes: - Cloudengine module_utils - the ``set-id`` (RPC-REPLY XML attribute) may change over the time althougth ``set-id`` is the identity of the next RPC packet. - Cloudengine netconf plugin - add a dispatch RPC function,just return original RPC-REPLY, the function is used by ``Cloudengine module_utils``. - Fixes in network action plugins to work in network connection plugin and modules in collection - Make netconf plugin configurable to set ncclient device handler name in netconf plugin (https://github.com/ansible/ansible/pull/65718) - Some cloudengine modules have options which should have been removed for Ansible 2.9. see https://github.com/ansible/ansible/issues/67020 and https://github.com/ansible-collections/community.network/pull/68 - Some cloudengine modules were missing ``import __future__`` and ``metaclass``. (https://github.com/ansible/ansible/pull/67634). - Some cloudengine modules were missing ``import __future__`` and ``metaclass``. (https://github.com/ansible/ansible/pull/67635). - action/ce - fix a bug, some new version os will not discard uncommitted configure with a return directly.(https://github.com/ansible/ansible/pull/63513). - ce - Modify exception handling method to make display information more obvious (https://github.com/ansible-collections/community.network/pull/51). - ce - Modify the way of parsing NETCONF XML message in ce.py (https://github.com/ansible-collections/community.network/pull/39). - ce_config - fixed issue - Re-building commands(config src) by replacing '#' with 'quit','quit' commands may close connection (https://github.com/ansible/ansible/issues/62872) - ce_is_is_interface - fix compile error for Python 3.9 (https://github.com/ansible-collections/community.network/pull/36). - edgeos_config - fix issue where module would silently filter out encrypted passwords - edgeos_config - fixed issue of handling single quotation marks. Now fails when unmatched (odd numbers) - edgeos_config - fixed issue where any change in check mode would cause all subsequent tasks to be treated as changes - netscaler_nitro_request - use all filters for get_filtered instead of only the first one (https://github.com/ansible-collections/community.network/issues/48). - plugins-netconf-ce - Fix failed to get version information. - plugins-netconf-ce - to get attribute 'set-id' from rpc-reply. - routeros module_utils - created a ``try``/``except`` block on the function ``get_capabilities`` (https://github.com/ansible-collections/community.network/pull/27). - routeros_facts - Prevent crash of module when ``ipv6`` package is not installed minor_changes: - ce_bgp_neighbor_af - Rename the parameter ``redirect_ip_vaildation`` to ``redirect_ip_validation`` (https://github.com/ansible/ansible/pull/62403). release_summary: 'This is the first proper release of the ``community.network`` collection on 2020-06-20. The changelog describes all changes made to the modules and plugins included in this collection since Ansible 2.9.0. ' fragments: - 0.2.0.yml - 27-routeros-exception-catching.yml - 34-fix-edgeos_config-false-positives-in-check-mode.yml - 36-ce_is_is_interface-python-3.9.yml - 39-ce_modify_the_parse_mode.yml - 51-ce_modify_exception_handling_method.yml - 52-netscaler_nitro_request-use-all-filters.yaml - 6-routeros_facts-multiple-entries-per-iface.yml - 60569-plugins-netconf-ce.yml - 62403-ce_bgp_neighbor_af_fix_parameter_name.yml - 62587-module_utils-network-cloudengine.yml - 62872-ce_config_too_many_quit_close_connection.yml - 63362-remove-edgeos-filtering.yaml - 63513-ce_action_wait_prompt_trigger_time_out.yaml - 65065-plugins-netconf-ce-fix.yaml - 67500-fix-edgeos-config-single-quote-stripping.yaml - 67634-Update-to-add-missing-import.yml - 67635-Update-to-add-missing-import.yml - 68-cloudengine_module_utils_remove_deprecated_version_2.9.yml - netconf_plugin_device_handler.yml - network_action_plugin_fixes.yml - routeros_facts-ipv6-crash.yml modules: - description: Run arbitrary commands on APCON devices name: apconos_command namespace: network.apconos - description: Manages isis process id configuration on HUAWEI CloudEngine devices. name: ce_is_is_instance namespace: network.cloudengine - description: Manages isis interface configuration on HUAWEI CloudEngine devices. name: ce_is_is_interface namespace: network.cloudengine - description: Manages isis view configuration on HUAWEI CloudEngine devices. name: ce_is_is_view namespace: network.cloudengine - description: Manages Eth-Trunk interfaces on HUAWEI CloudEngine switches name: ce_lacp namespace: network.cloudengine - description: Manages LLDP configuration on HUAWEI CloudEngine switches. name: ce_lldp namespace: network.cloudengine - description: Manages INTERFACE LLDP configuration on HUAWEI CloudEngine switches. name: ce_lldp_interface namespace: network.cloudengine - description: Manages MDN configuration on HUAWEI CloudEngine switches. name: ce_mdn_interface namespace: network.cloudengine - description: Manages multicast global configuration on HUAWEI CloudEngine switches. name: ce_multicast_global namespace: network.cloudengine - description: Manages multicast igmp enable configuration on HUAWEI CloudEngine switches. name: ce_multicast_igmp_enable namespace: network.cloudengine - description: Manages static route configuration on HUAWEI CloudEngine switches. name: ce_static_route_bfd namespace: network.cloudengine - description: Manage L2 interfaces on Extreme Networks EXOS devices. name: exos_l2_interfaces namespace: network.exos - description: Manage link layer discovery protocol (LLDP) attributes of interfaces on EXOS platforms. name: exos_lldp_interfaces namespace: network.exos - description: Manage VLANs on Extreme Networks EXOS devices. name: exos_vlans namespace: network.exos - description: Configures AAA parameters name: onyx_aaa namespace: network.onyx - description: Configures BFD parameters name: onyx_bfd namespace: network.onyx - description: Manage NTP general configurations and ntp keys configurations on Mellanox ONYX network devices name: onyx_ntp namespace: network.onyx - description: Configures NTP peers and servers parameters name: onyx_ntp_servers_peers namespace: network.onyx - description: Manages SNMP general configurations on Mellanox ONYX network devices name: onyx_snmp namespace: network.onyx - description: Configures SNMP host parameters name: onyx_snmp_hosts namespace: network.onyx - description: Configures SNMP User parameters name: onyx_snmp_users namespace: network.onyx - description: Configure file management syslog module name: onyx_syslog_files namespace: network.onyx - description: Configure remote syslog module name: onyx_syslog_remote namespace: network.onyx - description: Configure username module name: onyx_username namespace: network.onyx release_date: '2020-06-20' 1.0.0: changes: bugfixes: - edgeos_config - Added `cat` command to allow display of large files without `less`. Led to a timeout error. (https://github.com/ansible-collections/community.network/issues/79) - edgeos_config - fixed issue where config could be saved while in check mode (https://github.com/ansible-collections/community.network/pull/78) - edgeos_facts - Added `cat` command to allow display of large files without `less`. Led to a timeout error. (https://github.com/ansible-collections/community.network/issues/79) release_summary: 'This is release 1.0.0 of ``community.network``, released on 2020-07-31. ' removed_features: - onyx - all onyx modules and plugins have been moved to the mellanox.onyx collection. Redirects have been added that will be removed in community.network 2.0.0 (https://github.com/ansible-collections/community.network/pull/83). fragments: - 1.0.0.yml - 83-remove-onyx.yml - fix_edgeos_facts_and_edgeos_cli.yml - prevent-edgeos_config-saving-in-check-mode.yaml release_date: '2020-07-31' 1.1.0: changes: minor_changes: - cnos terminal plugin - prevent timeout connection failure by adding "no logging terminal" after log in (https://github.com/ansible-collections/community.network/pull/16). release_summary: 'Release for Ansible 2.10.0. ' fragments: - 1.1.0.yml - terminal_plugin_cnos_update.yml modules: - description: Ansible module for RouterOS API name: routeros_api namespace: network.routeros release_date: '2020-08-18' 1.2.0: changes: minor_changes: - edgeswitch_facts - added ``startupconfig`` to facts module - to allow the comparision between startup and running config (https://github.com/ansible-collections/community.network/pull/105). - routeros_facts - now also collecting data about BGP and OSPF (https://github.com/ansible-collections/community.network/pull/101). - routeros_facts - set configuration export on to verbose, for full configuration export (https://github.com/ansible-collections/community.network/pull/104). release_summary: Regular bimonthly minor release. fragments: - 1.2.0.yml - 101_update_routeros_facts.yml - 104_routeros_facts_export_verbose.yml - 105_edgeswitch_add-startupconfig.yml release_date: '2020-09-30' 1.3.0: changes: bugfixes: - action pugins - add check for network_cli connection type (https://github.com/ansible-collections/community.network/issues/119, https://github.com/ansible-collections/community.network/pull/120). - api - fix crash when the ``ssl`` parameter is used (https://github.com/ansible-collections/community.routeros/pull/3). - dladm_vnic - fixed issue where setting vlan in Python 3 caused a type error (https://github.com/ansible-collections/community.network/issues/131). - dladm_vnic - vlan IDs 0 and 4095 are now correctly identified as invalid (https://github.com/ansible-collections/community.network/pull/132). - fortimanager httpapi plugin - fix imports to load module_utils from fortios.fortimanager, where it actually exists. Please note that you must have the fortios.fortimanager collection installed for the plugin to work (https://github.com/ansible-collections/community.network/pull/151). - ftd httpapi plugin - make sure that plugin errors out on initialization if the required library is not found, and not on load-time (https://github.com/ansible-collections/community.network/pull/150). - routeros terminal plugin - allow slashes in hostnames for terminal detection. Without this, slashes in hostnames will result in connection timeouts (https://github.com/ansible-collections/community.network/pull/138). deprecated_features: - Deprecate connection=local support for network platforms using persistent framework (https://github.com/ansible-collections/community.network/pull/120). major_changes: - 'For community.network 2.0.0, the ``routeros`` modules and plugins will be moved to the `community.routeros `_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything. If you use Ansible 2.9 and explicitly use ``routeros`` content from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.routeros.`` instead of ``community.network.routeros_``, for example replace ``community.network.routeros_api`` in a task by ``community.routeros.api``. If you use ansible-base and installed ``community.network`` manually and rely on the ``routeros`` content, you have to make sure to install the ``community.routeros`` collection as well. If you are using FQCNs, i.e. ``community.network.routeros_command`` instead of ``routeros_command``, it will continue working, but we still recommend to adjust the FQCNs as well. ' - In community.network 2.0.0, the ``fortimanager`` httpapi plugin will be removed and replaced by a redirect to the corresponding plugin in the fortios.fortimanager collection. For Ansible 2.10 and ansible-base 2.10 users, this means that it will continue to work assuming that collection is installed. For Ansible 2.9 users, this means that they have to adjust the FQCN from ``community.network.fortimanager`` to ``fortios.fortimanager.fortimanager`` (https://github.com/ansible-collections/community.network/pull/151). release_summary: This is the last minor 1.x.0 release. The next releases from the stable-1 branch will be 1.3.y patch releases. fragments: - 1.3.0.yml - 119_fix_connection_check_issue.yml - 131_dladm_vnic.yml - 138-routeros-allow-slash.yml - fortimanager-imports.yml - ftd-imports.yml - routeros-3-api-ssl.yml - routeros-migration.yml release_date: '2020-11-25' 1.3.1: changes: major_changes: - 'For community.network 2.0.0, the Cisco NSO modules will be moved to the `cisco.nso `_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything. If you use Ansible 2.9 and explicitly use Cisco NSO modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``cisco.nso.`` instead of ``community.network.``, for example replace ``community.network.nso_config`` in a task by ``cisco.nso.nso_config``. If you use ansible-base and installed ``community.network`` manually and rely on the Cisco NSO modules, you have to make sure to install the ``cisco.nso`` collection as well. If you are using FQCNs, for example ``community.network.nso_config`` instead of ``nso_config``, it will continue working, but we still recommend to adjust the FQCNs as well. ' - 'For community.network 2.0.0, the FortiOS modules will be moved to the `community.fortios `_ collection. A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything. If you use Ansible 2.9 and explicitly use FortiOS modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.fortios.`` instead of ``community.network.``, for example replace ``community.network.fmgr_device`` in a task by ``community.fortios.fmgr_device``. If you use ansible-base and installed ``community.network`` manually and rely on the FortiOS modules, you have to make sure to install the ``community.fortios`` collection as well. If you are using FQCNs, for example ``community.network.fmgr_device`` instead of ``fmgr_device``, it will continue working, but we still recommend to adjust the FQCNs as well. ' release_summary: This release contains no code changes, only announcements in the changelogs and changes to CI. fragments: - 1.3.1.yml - cisco-migration.yml - fortios-migration.yml release_date: '2021-01-23' 1.3.2: changes: release_summary: Security bugfix (potential information leaks in multiple modules, CVE-2021-20191) release. security_fixes: - ce_vrrp - mark the ``auth_key`` parameter as ``no_log`` to avoid leakage of secrets (https://github.com/ansible-collections/community.network/pull/206). - cloudengine/ce_vrrp - enabled ``no_log`` for the options ``auth_key`` to prevent accidental disclosure (CVE-2021-20191, https://github.com/ansible-collections/community.network/pull/203). - cnos_* modules - mark the ``passwords`` parameter as ``no_log`` to avoid leakage of secrets (https://github.com/ansible-collections/community.network/pull/206). - enos_* modules - mark the ``passwords`` parameter as ``no_log`` to avoid leakage of secrets (https://github.com/ansible-collections/community.network/pull/206). - iap_start_workflow - mark the ``token_key`` parameter as ``no_log`` to avoid leakage of secrets (https://github.com/ansible-collections/community.network/pull/206). - icx_system - mark the ``auth_key`` parameter as ``no_log`` to avoid leakage of secrets (https://github.com/ansible-collections/community.network/pull/206). - itential/iap_start_workflow - enabled ``no_log`` for the options ``token_key`` to prevent accidental disclosure (CVE-2021-20191, https://github.com/ansible-collections/community.network/pull/203). - netscaler/netscaler_lb_monitor - enabled ``no_log`` for the options ``radkey`` to prevent accidental disclosure (CVE-2021-20191, https://github.com/ansible-collections/community.network/pull/203). - netscaler_lb_monitor - mark the ``password`` and ``secondarypassword`` parameters as ``no_log`` to avoid leakage of secrets (https://github.com/ansible-collections/community.network/pull/206). fragments: - 1.3.2.yml - CVE-2021-20191_no_log.yml - no_log-fixes.yml release_date: '2021-02-09'