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

Update the import system for Pipelines

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • pipe_base
    • None
    • 4
    • DRP F20-5 (Oct)
    • Data Release Production
    • No

    Description

      This ticket will be a tweak to how the import system works.

      This will include changing the top level section from 'inherits' to 'imports'. The later term seemed to be more confusing as it carried a lot of OO meaning in it. The old 'inherits' key will continue to work but will raise a warning that it will be removed in 6 months.

      The other change is to the way instruments are handled. Instruments will now carry though in an import. This means if an imported `Pipeline` defines an instrument, the `Pipeline` importing it will then have the instrument set to that value if it is not defined. There can only be one instrument will defined for a `Pipeline` so if any conflicting instruments are defined an error will be generated.

      When importing a `Pipeline` there is now an optional instrument key, that allows an the instrument for the `Pipeline` being imported set to None during import. This may be important for instance when testing and do not want instrument overrides to be loaded.

      It will not be an error to define the same instrument more than once.

      Attachments

        Issue Links

          Activity

            People

              nlust Nate Lust
              nlust Nate Lust
              Christopher Waters
              Christopher Waters, Nate Lust
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.