1. Proposed title of this feature request
[RFE] Local hosting for development artifacts

2. What is the nature and description of the request?

--> As a part of the artifacts deliverable by Satellite, it should be possible to include non-RPM content into Satellite.


3. Why does the customer need this? (List the business requirements here)

--> They want to have a single source of truth for building and delivering applications. Within that vision, it's expected that from a single system, they can build and deliver their applications with the right versioning, reproducibility, etc.

4. How would the customer like to achieve this? (List the functional requirements here)

- Current Satellite features are used to build a system.
- Additionally this system can download non-RPM content from their associated Content View.
- This content follows the same promotion rules (lifecycle environments) as regular CVs
- Promotion to capsules should be supported as well (same as CVs).
- There should be a way to query non-RPM files available to a particular system.

By non-RPM, it is understood:

- Regular binary files (eg: ZIP, TGZ)
- pip/python repos
- Java JAR/WAR/EAR


5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

--> Customer will provision a system, will check available non-RPM files and will initiate a download from the provisioned system.

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?

--> This RFE is highly based on https://bugzilla.redhat.com/show_bug.cgi?id=1124928 ; however that BZ points to Openshift and we believe this feature is better suited to be supported by Satellite.


7. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

--> As soon as possible, as subscription and contract management has been hightlighted as critical as to continue using Satellite.

8. List any affected packages or components.

Satellite 6.2


9. Would the customer be able to assist in testing this functionality if implemented?

Yes