cisco.meraki.networks_appliance_traffic_shaping_rules Always Pushes Configuration Even When Unchanged

[fdesouzabr]

I noticed that the cisco.meraki.networks_appliance_traffic_shaping_rules module in the Cisco Meraki Ansible collection appears to push configuration to the Meraki dashboard even when the existing configuration matches the desired state. This behavior seems unexpected, as it causes the task to be marked as "changed" even when no changes are actually required.

Upon checking the Meraki Dashboard logs, I observed that the same configuration is being pushed to the dashboard, even though it matches the existing configuration. This results in unnecessary API calls and could potentially impact automation workflows where maintaining consistency is expected.

Steps to Reproduce

• Ensure a traffic shaping rule is already configured on the Meraki dashboard, matching the desired configuration.
  

• Run a playbook using the cisco.meraki.networks_appliance_traffic_shaping_rules module with state: present and the same configuration as the dashboard.
  

• Observe the task result and behavior on the dashboard.
  

Expected Behavior

The task should detect that the existing configuration matches the desired state and report the task as "ok," without re-pushing the configuration to the dashboard.

Actual Behavior

The task pushes the configuration to the dashboard even when no changes are necessary, and the task is marked as "changed."

Environment Details

Ansible Version: 2.18.1
Meraki Collection Version: 2.18.3
Python Version: 3.12.3
Operating System: Ubuntu 22.04