Closed stephenprohaska closed 1 month ago
The "not an integer" errors are a bit of a red herring - it's just debugging that output because when it seems an integer there it treats it differently than when it's a string.
I suspect the volumes capacity
thing might be giving you trouble here - looking at their sample output, that seems like it's returning an array of two objects, and not something you can necessarily dig into and pluck just one value out.
To start with, I'd consider removing that specific mapping - and if everything works once you do that, we can see about possibly putting it back in.
You could try volumes 0 capacity
but I'm not necessarily convinced that would work - even though, like I said, we are doing some integer business in there.
That looks like it was correct! Removing that mapping resolved that error.
I did try volumes 0 capacity
and was not met with much luck unfortunately
After testing again, volumes 0 capacity
did appear to work! Marking this closed
I'm working on setting up the Kandji2Snipe integration for my org's hosted SnipeIT instance, and I'm running into issues when using the api mapping function
I have the following options set-up in my config file:
I'm running the script with the following arguments:
./kandji2snipe --mac --auto_incrementing --do_not_update_kandji --ratelimited
Things will go fine until it actually goes to write any of the selected values back to SnipeIT, at which time it will error out with the following info:
When I run the script with the
--dryrun
argument, it does not indicate that there are any issues. The errors only occur when it attempts to write data back to SnipeIT. Any advice or recommendations are appreciated