1. Proposed title of this feature request Provide a Python SDK for API consumption 3. What is the nature and description of the request? A Python SDK should be provided, documented and supported for easier consumption of the Satellite 6 API in Python. A Python SDK is already available for RHEV, this request is about providing equivalent SDK covering the Satellite 6 API. 4. Why does the customer need this? (List the business requirements here) To facilitate the consumption of the Satellite 6 API in Python code. 5. How would the customer like to achieve this? (List the functional requirements here) - A Python SDK for Satellite 6 is provided. - The Python SDK provides the same level of functionality that is currently available in the REST API. - The Python SDK is properly documented. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. - The Python SDK can be downloaded and installed. - The Python SDK provides methods for all the currently available API calls and supports all options already available. - The documentation for Python SDK can be downloaded or reviewed online and covers all aspects of the SDK. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? Somewhat related bug 1266580 (closed as wontfix). 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? Satellite 6.3. 9. Is the sales team involved in this request and do they have any additional input? Yes. 10. List any affected packages or components. N/A 11. Would the customer be able to assist in testing this functionality if implemented? Yes.
Would https://github.com/SatelliteQE/nailgun/ meet your needs?
possible duplicate of Bug 1266580 - [RFE] python API to interact with hammer
Lets try to deliver nailgun as part of 6.3
Per 6.3 planning, moving out non acked bugs to the backlog
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.