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

LTD Keeper: More Robust Edition purges

    Details

      Description

      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.

        Attachments

          Activity

          Hide
          jsick Jonathan Sick added a comment -

          Self-merged; in production and tested.

          Show
          jsick Jonathan Sick added a comment - Self-merged; in production and tested.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel