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_switchport access_policy_types choices don't match. #227

Closed
jeffkala opened this issue Apr 6, 2021 · 2 comments · Fixed by #228
Closed

meraki_switchport access_policy_types choices don't match. #227

jeffkala opened this issue Apr 6, 2021 · 2 comments · Fixed by #228
Assignees

Comments

@jeffkala
Copy link
Contributor

jeffkala commented Apr 6, 2021

The Ansible Module has choices:
access_policy_type:
choices: [Open, Custom access policy, MAC whitelist, Sticky MAC whitelist].

When a playbook uses this keyword, it will fail.

 "msg": "HTTP error 400 - https://api.meraki.com/api/v1/devices/Q2HP-HMV3-8PZW/switch/ports/6 - 'accessPolicyType' must be one of: 'Open', 'Custom access policy', 'MAC allow list' or 'Sticky MAC allow list'",
"response": "OK (unknown bytes)",
"status": 400

Looking at API docs, the valid options are listed in the schema.
https://developer.cisco.com/meraki/api-v1/#!update-device-switch-port

accessPolicyType:
string
The type of the access policy of the switch port. Only applicable to access ports. Can be one of 'Open', 'Custom access policy', 'MAC allow list' or 'Sticky MAC allow list'.

Fix is to change the choices in the arg_spec to the accurate options, which are 'Open', 'Custom access policy', 'MAC allow list' or 'Sticky MAC allow list'.

@jeffkala
Copy link
Contributor Author

jeffkala commented Apr 6, 2021

This can be assigned to me. Will be updating this along with adding additional functionality to this module.

@kbreit
Copy link
Collaborator

kbreit commented Apr 6, 2021

Thank you for the report. I set you as assigned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants