Create v5 Clone of Licensify DocDB in Integration #3928
Description
User Need
As a Platform Engineer
I want to create a DocumentDB v5 clone of Licensify DocDB in Integration
so that the Licensify maintainers can test compatibility (and upgrade) Licensify to support DocDB v5
Context
(Add any extra context, links, diagrams, stakeholder interviews, etc.)
Introduction
We have been outlining the steps required to support the DocumentDB version change. Our first priority is restoring and verifying the working state of the integration and staging systems. While initial inspection suggests a few existing issues, we are focused on ensuring these do not impede the migration process, but we will raise these with yourselves in due course.
The Plan
We would like to move forward with your offer to dump and restore the DocumentDB instance onto a cloned version. We will then point the integration environment at this clone and perform manual testing across enabled pages and services to ensure stability.
If we encounter significant issues with the database that cannot be resolved in place, our fallback is to build a standalone setup in our own environment to isolate and test changes. Once validated, you can either repeat the migration on the live integration environment or continue using the clone—whichever fits your workflow best. This can then be replicated for Staging and Production in due course.
What’s Needed
List anything the solution must do or be (behaviour, performance, security, UX, etc.).
- Create a carbon-copy of Licensify DocumentDB in Integration that is upgraded to DocumentDB Version 5
- Work with the maintainers in #gds-apto-collaboration to give them the necessary endpoints etc.
- Document any observations, caveats or limitations in doing the upgrade
Acceptance Criteria
Clear, measurable conditions to verify the story is complete and valuable.
- The maintainers in #gds-apto-collaboration confirm they have what they need to carry out their upgrade works
User Comms Plan (if applicable)
Briefly describe how you’ll let users know about the change.
- Communicate with #gds-apto-collaboration