Update Ansible collection community.routeros to v2.4.0 #257
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
| datasource | package | from | to | | ----------------- | ------------------ | ----- | ----- | | galaxy-collection | community.routeros | 2.3.1 | 2.4.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.3.1->2.4.0Release Notes
ansible-collections/community.routeros
v2.4.0Compare Source
======
Release Summary
Feature release improving the
api*modules.Minor Changes
force_no_certto connect with ADH ciphers (Add new api option force_no_cert ansible-collections/community.routeros#124).include_builtinwhich allows to include "builtin" entries that are automatically generated by ROS and cannot be modified by the user (make api_modify to ignore builtin items ansible-collections/community.routeros#130).interface bonding,interface bridge mlag,ipv6 firewall mangle,ipv6 nd,system scheduler,system script,system ups(support for new API paths and few updates ansible-collections/community.routeros#133).caps-man access-list,caps-man configuration,caps-man datapath,caps-man manager,caps-man provisioning,caps-man security(Capsman API paths ansible-collections/community.routeros#126).interface listandinterface list member(Interface list ansible-collections/community.routeros#120).interface pppoe-client,interface vlan,interface bridge,interface bridge vlan(Support for additional API paths ansible-collections/community.routeros#125).ip ipsec identity,ip ipsec peer,ip ipsec policy,ip ipsec profile,ip ipsec proposal(support for multiple "ip ipsec *" API paths ansible-collections/community.routeros#129).ip routeandip route vrf(Add support for ip route and ip route vrf ansible-collections/community.routeros#123).ipv6 address,ipv6 dhcp-server,ipv6 dhcp-server option,ipv6 route,queue tree,routing ospf area,routing ospf area range,routing ospf instance,routing ospf interface-template,routing pimsm instance,routing pimsm interface-template(multiple api paths support and updates ansible-collections/community.routeros#131).system logging,system logging action(system logging API paths ansible-collections/community.routeros#127).hw-offloadfor pathip firewall filter(api_modify, api_info: support more fields in existing paths ansible-collections/community.routeros#121).address-list,address-list-timeout,connection-bytes,connection-limit,connection-mark,connection-rate,connection-type,content,disabled,dscp,dst-address-list,dst-address-type,dst-limit,fragment,hotspot,icmp-options,in-bridge-port,in-bridge-port-list,ingress-priority,ipsec-policy,ipv4-options,jump-target,layer7-protocol,limit,log,log-prefix,nth,out-bridge-port,out-bridge-port-list,packet-mark,packet-size,per-connection-classifier,port,priority,psd,random,realm,routing-mark,same-not-by-dst,src-address,src-address-list,src-address-type,src-mac-address,src-port,tcp-mss,time,tls-host,ttlinip firewall natpath (support for new API paths and few updates ansible-collections/community.routeros#133).combo-mode,comment,fec-mode,mdix-enable,poe-out,poe-priority,poe-voltage,power-cycle-interval,power-cycle-ping-address,power-cycle-ping-enabled,power-cycle-ping-timeoutfor pathinterface ethernet(api_modify, api_info: support more fields in existing paths ansible-collections/community.routeros#121).jump-target,reject-withinip firewall filterAPI path, fieldcommentinip firwall address-listAPI path, fieldjump-targetinip firewall mangleAPI path, fieldcommentinipv6 firewall address-listAPI path, fieldsjump-target,reject-withinipv6 firewall filterAPI path (support for new API paths and few updates ansible-collections/community.routeros#133).interface gre,interface eoip(API update ansible-collections/community.routeros#128).blackhole,pref-src,routing-table,suppress-hw-offload,type,vrf-interfaceinip routepath (multiple api paths support and updates ansible-collections/community.routeros#131).system ntp client serversandsystem ntp serveravailable in ROS7, as well as new fieldsservers,mode, andvrfforsystem ntp client(adding "system ntp *" paths related to ROS7 ansible-collections/community.routeros#122).Bugfixes
ip routeentry can be defined without the need ofgatewayfield, which is correct for unreachable/blackhole type of routes (multiple api paths support and updates ansible-collections/community.routeros#131).queue interfacepath works now (multiple api paths support and updates ansible-collections/community.routeros#131).dynamicfrom API pathipv6 firewall address-list(support for new API paths and few updates ansible-collections/community.routeros#133).ingress-filteringininterface bridge portis nowtrue, which is the default in ROS (Support for additional API paths ansible-collections/community.routeros#125).Known Issues
queue treeare defined as human readable - for example25M-, the configuration will be correctly set in ROS, but the module will indicate the item is changed on every run even when there was no change done. This is caused by the ROS API which returns the number in bytes - for example25000000(which is inconsistent with the CLI behavior). In order to mitigate that, the limits have to be defined in bytes (those will still appear as human readable in the ROS CLI) (multiple api paths support and updates ansible-collections/community.routeros#131).routing ospf area,routing ospf area range,routing ospf instance,routing ospf interface-templatepaths are not fully implemeted for ROS6 due to the significat changes between ROS6 and ROS7 (multiple api paths support and updates ansible-collections/community.routeros#131).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.