BEFORE 27th
1. Set up PRs in preparation for go-live
Revalidation (New/current)
- see subtasksJira Legacy server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4235
- see subtasksJira Legacy server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4239 ALSO (see “TIS” section) For Revalidation API calls to work:
the admin needs to have the correct DBC assigned in usermanagement/profile service
And the RO for that DBC needs to be correct (in User Management)
Modify/Add reference “DBC” data
Revalidation (Old)
Not currently for this release plan
TIS
- see subtasksJira Legacy server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4236 Note: Flyway script to merge users for North Central & East London and North West London into new DBC (choose one to preserve and migrate the other for now) -
Jira Legacy server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4245 draft PRs:
- just subtask 4250 for nowJira Legacy server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4246
NDW
Could check reports ahead of time, but fairly confident that they’re fine.
2. Disable Reval Cron Jobs Temporarily from the 24th onwards
Set the following Parameter Store values to “-” and force redeployment of recommendations service in ECS:
/tis/revalidation/preprod/recommendation/cron/nightlysync
/tis/revalidation/preprod/recommendation/cron/recommendationstatuscheck
/tis/revalidation/prod/recommendation/cron/nightlysync
/tis/revalidation/prod/recommendation/cron/recommendationstatuscheck
...
AFTER 27th-29th
1. Get the new codes from GMC
We need the codes soon as they are available. This will require liaising with Holly via email.
2. Update and merge PRs when new codes are received
See section 1 for PRs
3. Deploy services once PRs are merged and Terraform changes applied
TIS TCS
TIS Reference
TIS Profile
GMC-Client
Revalidation Recommendations
Revalidation FE
4. Run jobs
GMC doctor sync - will take some time
Reval ES Rebuild - will take ~ 2 hours
Restore Cron Values
5. Force log in for all users
Do we need to be concerned about application users (e.g. for scheduled jobs)
6. Ask users to test
Can they log in
Can they see the doctors they should be able to see
Can they not see doctors they shouldn't be able to see
Can they submit a recommendation