merge latest and update per PR #142 comments

.github/BOTMETA.yml

@@ -36,9 +36,6 @@ files:
   $cliconfs/nos.py:
     maintainers: $team_extreme
     labels: networking nos
-  $cliconfs/routeros.py:
-    maintainers: heuels
-    labels: networking routeros
   $cliconfs/slxos.py:
     maintainers: $team_extreme
     labels: networking slxos
@@ -120,12 +117,6 @@ files:
   $module_utils/network/ordnance/ordnance.py:
     maintainers: alexanderturner djh00t
     labels: networking
-  $module_utils/network/panos/panos.py:
-    maintainers: ivanbojer jtschichold shinmog
-    labels: networking
-  $module_utils/network/routeros/routeros.py:
-    maintainers: heuels
-    labels: networking
   $module_utils/network/slxos/slxos.py:
     maintainers: $team_extreme
     labels: networking
@@ -321,41 +312,8 @@ files:
   $modules/network/ordnance/:
     authors: alexanderturner
     maintainers: djh00t
-  $modules/network/panos/:
-    authors: ivanbojer jtschichold
-    maintainers: shinmog
-  $modules/network/panos/panos_commit.py:
-    authors: ivanbojer jtschichold traittinen
-  $modules/network/panos/panos_dag_tags.py:
-    authors: vinayvenkat
-    maintainers: ivanbojer jtschichold shinmog
-  $modules/network/panos/panos_match_rule.py:
-    authors: rnh556
-    maintainers: ivanbojer jtschichold shinmog
-  $modules/network/panos/panos_nat_rule.py:
-    authors: ivanbojer jtschichold rnh556
-  $modules/network/panos/panos_object.py:
-    authors: rnh556
-    maintainers: ivanbojer jtschichold shinmog
-  $modules/network/panos/panos_op.py:
-    authors: ivanbojer
-    maintainers: jtschichold shinmog
-  $modules/network/panos/panos_query_rules.py:
-    authors: rnh556
-    maintainers: ivanbojer jtschichold shinmog
-  $modules/network/panos/panos_sag.py:
-    authors: vinayvenkat
-    maintainers: ivanbojer jtschichold shinmog
-  $modules/network/panos/panos_security_rule.py:
-    authors: ivanbojer rnh556
-    maintainers: jtschichold shinmog
-  $modules/network/panos/panos_set.py:
-    authors: spmp
-    maintainers: ivanbojer jtschichold shinmog
   $modules/network/radware/:
     authors: evgenyfedoruk
-  $modules/network/routeros/:
-    authors: heuels
   $modules/network/slxos/:
     authors: bigmstone
     maintainers: LindsayHill ujwalkomarla
@@ -392,9 +350,6 @@ files:
   $terminals/nos.py:
     maintainers: $team_extreme
     labels: networking nos
-  $terminals/routeros.py:
-    maintainers: heuels
-    labels: networking routeros
   $terminals/slxos.py:
     maintainers: $team_extreme
     labels: networking slxos
@@ -421,9 +376,11 @@ macros:
   modules: plugins/modules
   terminals: plugins/terminal
   team_aci: aciguru brunocalogero devarshishah3 fadallar jmcgill298 koladiya mtorelli rsmeyers schunduri smnmtzgr
+  team_aruba: karthikeyan-dhandapani
   team_avi: ericsysmin grastogi23 khaltore
   team_e_spirit: MatrixCrawler getjack
   team_extreme: LindsayHill bigmstone ujwalkomarla
+  team_ftd: annikulin
   team_huawei: QijunPan TommyLike edisonxiang freesky-edward hwDCN niuzhenguo xuxiaowei0512 yanzhangi zengchen1024 zhongjun2
   team_lenovo: istaicu mihaibroc
   team_netscaler: chiradeep giorgos-nikolopoulos

changelogs/fragments/check_point-migration.yml

@@ -0,0 +1,15 @@
+removed_features:
+- >
+  The ``cp_publish`` module has been removed from this collection.
+  It was a duplicate of ``check_point.mgmt.cp_mgmt_publish`` in the `check_point.mgmt <https://galaxy.ansible.com/check_point/mgmt>`_ collection.
+  If you use ansible-base 2.10 or newer, redirections have been provided.
+
+  If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.cp_publish`` → ``check_point.mgmt.cp_mgmt_publish``) and make sure to install the check_point.mgmt collection.
+- The dependency on the ``check_point.mgmt`` collection has been removed. If you depend on that installing ``community.network`` also installs ``check_point.mgmt``, you have to make sure to install ``check_point.mgmt`` explicitly.
+breaking_changes:
+- >
+  If you use Ansible 2.9 and the ``cp_publish`` module from this collection, community.network 2.0.0 results in errors when trying to use the module by FQCN, i.e. ``community.network.cp_publish``.
+  Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``check_point.mgmt.cp_mgmt_publish``) and to make sure that you have ``check_point.mgmt`` installed.
+
+  If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``check_point.mgmt`` if you are using the ``cp_publish`` module.
+  While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (check_point.mgmt) must be installed for them to work.

changelogs/fragments/fortimanager-imports.yml

@@ -0,0 +1,4 @@
+bugfixes:
+- "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)."
+major_changes:
+- "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)."

changelogs/fragments/ftd-imports.yml

@@ -0,0 +1,2 @@
+bugfixes:
+- "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)."

changelogs/fragments/netcommon_ipaddress.yaml

@@ -0,0 +1,7 @@
+---
+breaking_changes:
+  - cnos_static_route - move ipaddress import from ansible.netcommon to builtin
+    or package before ipaddress is removed from ansible.netcommon. You need to
+    make sure to have the ipaddress package installed if you are using this
+    module on Python 2.7
+    (https://github.com/ansible-collections/community.network/pull/129).

changelogs/fragments/nso-migration-removal.yml

@@ -0,0 +1,14 @@
+removed_features:
+- |
+  All ``nso`` modules have been removed from this collection.
+  They have been migrated to the `cisco.nso <https://galaxy.ansible.com/cisco/nso>`_ collection.
+  If you use ansible-base 2.10 or newer, redirections have been provided.
+
+  If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.nso_config`` → ``cisco.nso.nso_config``) and make sure to install the `cisco.nso` collection.
+breaking_changes:
+- |
+  If you use Ansible 2.9 and the ``nso`` modules from this collection, community.network 2.0.0 results in errors when trying to use the nso content by FQCN, like ``community.network.nso_config``.
+  Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``cisco.nso.nso_config`` for the previous example) and to make sure that you have ``cisco.nso`` installed.
+
+  If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``cisco.nso`` if you are using any of the ``nso`` modules.
+  While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (cisco.nso) must be installed for them to work.

changelogs/fragments/remove-deprecated-modules.yml

@@ -0,0 +1,3 @@
+removed_features:
+- The deprecated Pluribus Networks modules ``pn_cluster``, ``pn_ospf``, ``pn_ospfarea``, ``pn_show``, ``pn_trunk``, ``pn_vlag``, ``pn_vlan``, ``pn_vrouter``, ``pn_vrouterbgp``, ``pn_vrouterif``, ``pn_vrouterlbif`` have been removed (https://github.com/ansible-collections/community.network/pull/176).
+- The deprecated modules ``panos_admin``, ``panos_admpwd``, ``panos_cert_gen_ssh``, ``panos_check``, ``panos_commit``, ``panos_dag``, ``panos_dag_tags``, ``panos_import``, ``panos_interface``, ``panos_lic``, ``panos_loadcfg``, ``panos_match_rule``, ``panos_mgtconfig``, ``panos_nat_rule``, ``panos_object``, ``panos_op``, ``panos_pg``, ``panos_query_rules``, ``panos_restart``, ``panos_sag``, ``panos_security_rule``, ``panos_set`` have been removed. Use modules from the `paloaltonetworks.panos collection <https://galaxy.ansible.com/paloaltonetworks/panos>`_ instead (https://github.com/ansible-collections/community.network/pull/176).

changelogs/fragments/remove-deprecated-redirects.yml

@@ -0,0 +1,2 @@
+removed_features:
+- "The redirect to the ``mellanox.onyx`` collection was removed for: the ``onyx`` cliconf plugin, terminal plugin, module_utils, action plugin, doc fragment, and the following modules: ``onyx_aaa``, ``onyx_bfd``, ``onyx_bgp``, ``onyx_buffer_pool``, ``onyx_command``, ``onyx_config``, ``onyx_facts``, ``onyx_igmp``, ``onyx_igmp_interface``, ``onyx_igmp_vlan``, ``onyx_interface``, ``onyx_l2_interface``, ``onyx_l3_interface``, ``onyx_linkagg``, ``onyx_lldp``, ``onyx_lldp_interface``, ``onyx_magp``, ``onyx_mlag_ipl``, ``onyx_mlag_vip``, ``onyx_ntp``, ``onyx_ntp_servers_peers``, ``onyx_ospf``, ``onyx_pfc_interface``, ``onyx_protocol``, ``onyx_ptp_global``, ``onyx_ptp_interface``, ``onyx_qos``, ``onyx_snmp``, ``onyx_snmp_hosts``, ``onyx_snmp_users``, ``onyx_syslog_files``, ``onyx_syslog_remote``, ``onyx_traffic_class``, ``onyx_username``, ``onyx_vlan``, ``onyx_vxlan``, ``onyx_wjh`` (https://github.com/ansible-collections/community.network/pull/175)."

changelogs/fragments/routeros-migration-removal.yml

@@ -0,0 +1,14 @@
+removed_features:
+- |
+  All ``routeros`` modules and plugins have been removed from this collection.
+  They have been migrated to the `community.routeros <https://galaxy.ansible.com/community/routeros>`_ collection.
+  If you use ansible-base 2.10 or newer, redirections have been provided.
+
+  If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.network.routeros_command`` → ``community.routeros.command``) and make sure to install the community.routeros collection.
+breaking_changes:
+- |
+  If you use Ansible 2.9 and the ``routeros`` plugins or modules from this collections, community.network 2.0.0 results in errors when trying to use the routeros content by FQCN, like ``community.network.routeros_command``.
+  Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.routeros.command`` for the previous example) and to make sure that you have ``community.routeros`` installed.
+
+  If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.network manually, you need to make sure to also install ``community.routeros`` if you are using any of the ``routeros`` plugins or modules.
+  While ansible-base 2.10 or newer can use the redirects that community.network 2.0.0 adds, the collection they point to (community.routeros) must be installed for them to work.

galaxy.yml

@@ -1,6 +1,6 @@
 namespace: community
 name: network
-version: 1.3.0
+version: 2.0.0
 readme: README.md
 authors:
   - Ansible (https://github.com/ansible)
@@ -10,7 +10,6 @@ tags: [community, network]
 # NOTE: No more dependencies can be added to this list
 dependencies:
   ansible.netcommon: '>=1.0.0'
-  check_point.mgmt: '>=1.0.0'
   fortinet.fortios: '>=1.0.0'
 repository: https://github.com/ansible-collections/community.network
 documentation: https://docs.ansible.com/ansible/latest/collections/community/network/