Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-895

Fix our requirements setup for insights and standalone modes

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Backend
    • False
    • False

      Issue:

      We have requirements.standalone.in|txt and requirements.insights.in|txt files where the .txt files build from setup.py and the .in files. Our setup.py includes common dependencies and .in include deployment mode dependencies. However, RPMs that build for standalone mode currently need all dependencies in setup.py.

      Proposed fix:

      Add something like this to setup.py (see this for possible reference: https://github.com/rochacbruno/python-project-template/blob/main/setup.py#L24-L29):

      extras_require = {
          "standalone": read("requirements/requirements.standalone.in"),  # or txt?
          "insights": read("requirements/requirements.insights.in"),  # insights deps work today, but if we want to add this we may want to edit our Makefile pip-compile statements to use this to get to the ".in" file
      }
      

      Add graft requirements to MANIFEST.in

      Ensure pulp_installer team and the RPM build team can use these

            jtanner@redhat.com James Tanner
            awcrosby5 Andrew Crosby (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: