-
Notifications
You must be signed in to change notification settings - Fork 950
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
Test cases fail for interface type: other-wireless #1460
Comments
I just double checked and you are correct, the type Just let me know. Thanks for catching this! As a side note, we try to avoid using other in these definition files as much as possible. What interface type are you trying to add that does not already exist? |
other-wireless
other-wireless
I'm working on adding some Meraki wireless devices. A dedicated third radio provides real-time WIDS/WIPS, with automated RF optimization. Since the 3rd radio isn't used for data, Other (Wireless) seemed to fit best. If you'd prefer that one have another type I can go ahead an update those before I submit the PR that will be coming for that. I'll get a PR submitted to add other-wireless in a bit. |
Sounds good about Could you send me a link to the datasheet for the device with this radio? |
https://documentation.meraki.com/MR/MR_Overview_and_Specifications/MR46_Datasheet But to keep from cluttering this, if you'd rather we can discuss when I submit that PR. |
In the NetBox web ui there is an interface type of Other (Wireless) available. If a yaml file is created with the snippet below, the pre-commit script fails because schema/components.json is missing this definition.
I made sure this is the expected type by exporting a device via the web ui.
The text was updated successfully, but these errors were encountered: