Created a new subscription database field called 'next_templates'. The field will be populated gracefully as new cycles begin, or a safelisting report is requested. When a new cycle is started, the templates from the 'next_templates' field are moved into the 'templates_selected' field, and the 'next_templates' field is randomized with new templates.
💭 Motivation and context
Request from the client. Some customers want to be able to know the templates that will be used during the next cycle to aid in their safelisting practices.
🧪 Testing
Tested locally.
✅ Pre-approval checklist
[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
🗣 Description
Jira ticket: https://cset.atlassian.net/browse/CPD-1020
Backend changes: https://github.com/cisagov/con-pca-web/pull/429
Created a new subscription database field called 'next_templates'. The field will be populated gracefully as new cycles begin, or a safelisting report is requested. When a new cycle is started, the templates from the 'next_templates' field are moved into the 'templates_selected' field, and the 'next_templates' field is randomized with new templates.
💭 Motivation and context
Request from the client. Some customers want to be able to know the templates that will be used during the next cycle to aid in their safelisting practices.
🧪 Testing
Tested locally.
✅ Pre-approval checklist