Experimental/POC: template versioning

[Abi-Nada]

Description:

Epic: #6815

Documentation

Take a first pass at the database updates proposed in the above doc. ^

[timarney]

Database schema update has been merged -- this just adds the new versions table

#7280

Feature flag added

#7281

[timarney]

Step 1 PR to allow editing a published template

• Writes to the new versions table
• Keeps the current jsonConfig in the "non-versioned" Templates table in back for full backwards compatibility
• Adds link to edit + updates for Publish modal etc... for republish

PR #7277

Note:

This PR only updates the template config

Follow up PRs will happen for

• Responses UI
• Response Pilot
• API

☝️ These all need further discussion --- re: how to update the UI and API endpoints to handle versioned responses

Current:

wip.mp4

[Abi-Nada]

Submissions and responses -- need higher level conversation (1 hour meeting)

Bryan and Clement have availability/capacity between Wednesday - Friday for a sync ^

[anikbrazeau]

Set up two alignment meetings to discuss implications / considerations for this work:

1. Responses UI / Formats / Pilot --> Tuesday afternoon
2. API retrieval / Integrations / Breaking changes --> Thursday morning

Before coding anything, we need to figure out all the aspects/limitations involved and chart a way forward.

[timarney]

On the infra end:

Index update has been merged

cds-snc/forms-terraform#1365

PR

cds-snc/forms-terraform#1358 is being worked on which updates code needed to accept a "versioned" response

[timarney]

POC --

• For creating versioned templates
• Submitting versioned responses

#7341

• Retrieving versioned responses

#7313

is "done enough" to have a good understanding of tech challenges

@dsamojlenko is working to better organize / shrink the amount of template queries we have in the current code base ... this will make the job of porting to "versioned" equivalents easier + less queries to maintain as we transition.

[anikbrazeau]

Update from standup

• New index on dynamoDB vault table, migrate app and API to use new index, similar to a bunch of steps with “Status created at” index
• Potential of 20 minutes of downtime if we take a shortcut

[anikbrazeau]

Update from sprint planning

• Clement working on the API side (return version when get a response, fetch any version of the template through the API)
• Dave working on refactoring template library, next step

[anikbrazeau]

Standup update

• Did refactoring to support this
• Brought prototype work into new codebase