Retain 30 days of Forms migration CSVs, date-stamped, for triage purposes

[jilladams]

User story

AS A VA Form product team member I WANT access to Forms migration logs from the last 30 days SO THAT I can easily tell whether migration data on a specific date in the past is the root cause of a form edit or not

Description

We currently retain the most recent Forms MIgration CSV: https://prod.cms.va.gov/admin/structure/migrate/manage/forms/migrations/va_node_form/source

Sometimes, an issue pops up several days after a migration, and we no longer have that night's CSV, to be able to inspect what changes it introduced. This slows down triage, and the process of deducing whether a bug was actually caused by Forms migration, or has a different root cause.

We want to retain 30 days of Forms migration CSVs, to resolve.

Engineering notes / background

Testing & QA

Scope / Impact analysis

What, if anything, could break as a result of this change? Engineer should assess this when approaching PR.

Roles / assignments

After functional testing, code review, accessibility review, and design review can happen in parallel.

• Functional testing:
• Code review:
• Product acceptance:

Acceptance criteria

_ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable._

• [ ]
• [ ] Impact analysis is filled out and QA test plan is updated accordingly
• [ ] Does this product have an existing regression test plan?
  • [ ] Yes, link:
  • [ ] No, regression test plan will be created as part of the work / points in this ticket

[jilladams]

Questions I have that may be a part of the task itself to figure out, or might be things to decide in refinement, not sure:

• Naming convention for the updated CSVs
• Once we store them, who can access them and how. (It would be very helpful for PM / DM to be able to access old logs, #19429 as case in point)