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

LTD Keeper: More Robust Edition purges



      LTD Keeper needs to purge Fastly when an Edition is rebuilt. Currently the surrogate-key for the build is also used to cover editions. This means that the key needed to purge an edition is the same as that for an build. Hence purging an edition means that the system needs to purge the surrogate key of the previous build.

      We're seeing situations where the surrogate key that Keeper is purging is not the one that needs to be purged. A more robust configuration would be for each edition to have a stable surrogate-key that can be unambiguously purged.

      This ticket covers the following work:

      1. Diagnose the issue.
      2. Enable Alembic migrations for Flask (Flask-Migrate)
      3. Add a surrogate-key column to the Edition model
      4. Change the S3 copy rebuild code to change the surrogate-key header
      5. Change the rebuild code to purge based on the edition's surrogate-key.



          jsick Jonathan Sick created issue -
          jsick Jonathan Sick made changes -
          Field Original Value New Value
          Epic Link DM-5858 [ 23985 ]
          jsick Jonathan Sick made changes -
          Status To Do [ 10001 ] In Progress [ 3 ]
          jsick Jonathan Sick made changes -
          Story Points 1.3 2.7
          jsick Jonathan Sick made changes -
          Labels lsst-the-docs lsst-the-docs ltd-keeper
          jsick Jonathan Sick made changes -
          Story Points 2.7 3.2
          jsick Jonathan Sick made changes -
          Resolution Done [ 10000 ]
          Status In Progress [ 3 ] Done [ 10002 ]


            • Assignee:
              jsick Jonathan Sick
              jsick Jonathan Sick
              Jonathan Sick
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Summary Panel