Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meraki_mx_l3_firewall - Fix firewall rules not updating #62

Merged
merged 2 commits into from
Feb 15, 2020

Conversation

kbreit
Copy link
Collaborator

@kbreit kbreit commented Feb 8, 2020

Firewall rules were not updating due to range() not working if there was only one non-default firewall rule. This pull request fixes this. I also discovered a bug with integration tests where any wasn't matching with the response from Meraki. I consulted Meraki and they clarified what I should expect. I've updated integration tests and documentation to reflect.

Fixes #61

CC @pokepoke81

- Any parameters with Any need to be capital except for protocol
- Update integration tests
@kbreit kbreit added the bug Something isn't working label Feb 8, 2020
@kbreit kbreit self-assigned this Feb 8, 2020
@kbreit kbreit merged commit 75f68b2 into CiscoDevNet:master Feb 15, 2020
@kbreit kbreit deleted the bugfix/61_mx_firewall branch February 15, 2020 02:53
kbreit added a commit to kbreit/ansible-meraki that referenced this pull request Jun 20, 2020
* Fix lack of updates when there is only 1 real rule

* Fix capitalization for Any
- Any parameters with Any need to be capital except for protocol
- Update integration tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ansible not updating MX L3 Firewall, but states success
1 participant