Async exports#6539
Draft
MartinVanIJcken wants to merge 32 commits intoasync-exports-models-and-jobsfrom
Draft
Conversation
MartinVanIJcken
force-pushed
the
async-exports
branch
12 times, most recently
from
38c59ca to
e7092aa
Compare
MartinVanIJcken
force-pushed
the
async-exports
branch
2 times, most recently
from
658d289 to
ac61c6b
Compare
MartinVanIJcken
force-pushed
the
async-exports
branch
from
ac61c6b to
9851c25
Compare
MartinVanIJcken
changed the base branch from
next
to
async-exports-models-and-jobs
MartinVanIJcken
force-pushed
the
async-exports
branch
from
9851c25 to
feb709e
Compare
MartinVanIJcken
force-pushed
the
async-exports-models-and-jobs
branch
from
d413eeb to
76dcf80
Compare
MartinVanIJcken
force-pushed
the
async-exports
branch
2 times, most recently
from
34783d1 to
a28703b
Compare
MartinVanIJcken
force-pushed
the
async-exports-models-and-jobs
branch
from
76dcf80 to
28b4897
Compare
MartinVanIJcken
force-pushed
the
async-exports-models-and-jobs
branch
from
28b4897 to
a2dc44b
Compare
MartinVanIJcken
force-pushed
the
async-exports
branch
from
a28703b to
5f72eb6
Compare
MartinVanIJcken
force-pushed
the
async-exports-models-and-jobs
branch
3 times, most recently
from
4dae2d6 to
c06aa50
Compare
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
This does not test the full journey as the form should be accessed from the reporting app normally, but here is accessed directly via the URL. Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
The reporing app sends users to vaccination-reports. In order to be consistent with the other exports, we want that route to be vaccination-records/exports. A PR will also be raised to the reporting app to change this route, but in order to allow for a zero downtime release, we should keep this URL functioning for some time until all sessions on the old reporting app have ended. Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Now that all routes go through the vaccination records export, this code is no longer needed. Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
Jira-Issue: MAV-1521
MartinVanIJcken
force-pushed
the
async-exports
branch
from
5f72eb6 to
da20ebf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces asynchronous downloads for our three main download types:
These downloads are created as a database object when requested by the user and an asynchronous Sidekiq job then generates their content while the user can continue to other tasks. After a 30 day wait, export data is removed to safe on storage.
Generated exports are shown on the new Manage Data page, which also contains the old imports page. The design closely matches but is not identical to the prototype to account for the fact that the imports page still needs to be redesigned.
The route vaccination-report was replaced by vaccination-records/export to match the other exporters. A redirect is now in place to redirect traffic from the reporting app. In a future release of the reporting app, the reporting app can be set to direct directly to vaccination-records/export and this redirect can be removed.
Jira Issue - MAV-1512
Jira Issue - MAV-3329
Screenshots
Screencast_20260416_125551.webm