3 ms·
Imagine an xmlrpc client module that could use any xmlrpc API and you wouldn't need one module for every task in the API. Which is the case now in the ansible m
by INTPenis 9y ago
Imagine an xmlrpc client module that could use any xmlrpc API and you wouldn't need one module for every task in the API. Which is the case now in the ansible modules.
But the module can't send an actual integer to the API if the API expects an int. It always came out as a string.
This is due to the issue with native types.
You could add logic to recognize integers and let users specify if they want integer conversion of values or not but that's a lot of extra crud for something that could be very simple.