Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-6332

Ensure configuration framework is included in long-term planning

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: pex_config
    • Labels:
      None
    • Templates:
    • Epic Link:
    • Team:
      System Management

      Description

      From Jim Bosch's technical debt list:

      pex_config has no active developers, leading to a long backlog of tickets and a stall in big-picture improvements. Code is hard to read/maintain, and design is exhibiting serious limitations when used in large pipelines, especially in lack of support for ways to connect related options in different sections of the tree. Serialization with plugins continues to be fragile. Distinctions between what-to-run and how-to-run options it are not well captured, leading to incorrect provenance when the same pipeline is executed at different levels. We still haven't dropped pex_policy. Provenance of configuration options is unnecessarily complex and developers are confused by --clobber-config behavior.

      My best guess is that this is 0.5 FTE ongoing.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbecla Jacek Becla
                Reporter:
                jbosch Jim Bosch
                Watchers:
                Fritz Mueller, Jacek Becla, Jim Bosch, Kian-Tat Lim
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel