Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
It's the most basic xmlrpc API client that forwards any call to the API along with positional arguments and keyword arguments. This way the ansible user can decide how to use the xmlrpc api along with the relevant API docs.
ISSUE TYPE
COMPONENT NAME
lib/ansible/modules/commands/xmlrpc_client
ANSIBLE VERSION
ADDITIONAL INFORMATION
I have an API internally where this module helps a lot because it lets me use ansible for the entire deployment process.
Looking at other ansible modules for xmlrpc APIs I can see that a basic xmlrpc client module would be able to perform their tasks as well but with less abstractions between the user and the API.
I wasn't sure which category to put the module in. I'm sure people will have issue with placing it under commands, in that case just know that I have no problem with moving it to another category if a more suitable one can be found.
I have run sanity checks and there is only one unresolved issue.
The docs say to use 1.0 so I can't resolve that.
This module will become more useful once #23943 is resolved. Until then this use will not send integer to the backend API.