1. Proposed title of this feature request Support for pip and easy_install custom repositories for offline use. 3. What is the nature and description of the request? A python s2i option to specify a private python repository that both PIP and easy_install will use. 4. Why does the customer need this? (List the business requirements here) The current s2i python images only support specifying custom pip repositories via the (undocumented in the python s2i docco) PIP_INDEX_URL environment variable. If one of the python dependencies need to be installed via easy_install, then python will fall back to trying to download the dependency via the internet python repositories. If the system is not internet connected, then the entire build process will fail. This practically makes python S2I useless in disconnected environments for anything other then toy examples. 5. How would the customer like to achieve this? (List the functional requirements here) Setting an argument for the S2I python assemble script will use to specify a python repo to place in templated files at ~/.pip/pip.conf (for use by pip) and a ~/.pydistutils.cfg (for use by easy_install). 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Test will be to run python s2i on a python repo that has a requirements.txt file that has pip and easy_install sub-dependencies. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No idea. 8. What information can you provide around timeframes and urgency? Python S2i in disconnected environment not really functional without this. 9. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? Rhel7 / ose 3.5 10. List any affected packages or components. Python S2I docker images. 11. Would the customer be able to assist in testing this functionality if implemented? Happy to help test out, but please understand there will be some latency in testing stuff and getting the results back to you.
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.