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

Remove configuration from obs_* packages after Gen2 removal

    XMLWordPrintable

    Details

    • Team:
      Data Release Production
    • Urgent?:
      No

      Description

      Complete the implementation of RFC-775 by removing config files from obs_ packages where possible; those that remain should meet the criteria that all invocations of the task for that instrument (in any configuration) should use that configuration, but invocations of the task for most other instruments should not.  Configuration should generally be moved to _pipe packages, either as config files or pieces of pipeline files.

      This is not doable until Gen2 has been retired, as we don't want to try to change where Gen2 looks up config files.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment - - edited

            I have added the remaining gen2 removal tickets that could block this. Although no obs packages support gen2 any more so I imagine that means this ticket can proceed.

            Show
            tjenness Tim Jenness added a comment - - edited I have added the remaining gen2 removal tickets that could block this. Although no obs packages support gen2 any more so I imagine that means this ticket can proceed.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jbosch Jim Bosch
              Watchers:
              Jim Bosch, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins Builds

                  No builds found.