The API team made an undocumented change and introduced a bug in November 2021 the week of Thanksgiving that changed the vlan return data type from integer to string. I confirmed it via the live documentation tool so I knew it wasn't the Python module that was doing it. When I caught it in my weekly report data the following week, I opened a support case with all the documentation on it I could put together on what had happened to point them to the source of the issue. I believe it was in February when I was officially informed by support they weren't going to fix it. Instead of fixing the bug, they just changed the documentation to match the mistake. When dealing with vlans, the vlan number is an integer, but when dealing clients the vlan is now a string. Does that make any sense? I had to rewrite portions of my weekly report program to deal with the mixed data types so it would work until they corrected it and so it would continue to work when they corrected it, which they chose not to do. I had to add the extra code because they can break things overnight, but it takes them at least two weeks and usually more to correct mistakes. They tried to pull that on vlans with the Python APIv1 module when it was in beta and I called it out. If you return me a value as an integer, you better accept it back as an integer. That issue was corrected in the module in the next beta release. Data types should be kept consistent across the board plain and simple. Mixing data types only adds frustration and unnecessary code to address it.
... View more