TP2000-1493 - TAP driven quota open data export

[dougmills-DIT]

TP2000-1493 TAP driven quota open data export

Why

• The current open data implementation is created from an SQL lite export imported into data workspace and queried via a static query stored in data-flow.
• The move from data workspace to TAP generated will speed the process up and allows more stringent testing to be automated around the output.
• Update have been made to the current implementation several times to resolve data inconsistency issues. Moving to within TAP will help reduce future issues as TAP is updated.
• Moving the creation of quotas open data is the first of several open data exports that would be better placed within TAP.

What

• Create process to export TAP quota data to a CSV file
• Add methods of storage for both S3 and local
• Unit test everything

Checklist

• Requires migrations? No
• Requires dependency updates? No

Links to relevant material
See: Description

[SteveCN7]

Silly question - the initial volume column, are we pulling that from TAP or OTT? I think we should be pulling it from TAP really if we're not already