Spike: Explore ways for customers to retain Duo access during extensions
<!--Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks. https://www.learning-styles-online.com/style/visual-spatial/--> ### Problem Currently, self managed extensions are granted by provisioning legacy trial licenses to customers. Given legacy licenses do not honor Duo features, customers lose access to it at the time of extension period. ### Proposal <!--Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved.--> Noting a few options discussed: ##### Option 1: Grant online cloud trial license instead of legacy license (depends on https://gitlab.com/groups/gitlab-org/-/epics/12173) ##### Option 2: Extend the validity of existing cloud license Currently, when self managed instances trigger seat syncs, they are provisioned with a new license key if there are any changes. We can utilize this functionality to check at the time of sync if a temporary extension exists for the subscription and create a new license with extended `expires_at` and `block_changes_at`. Given extensions can be granted **after** the term expires, we need to ensure the instances can trigger sync or use the manual sync. ### Result Customer is able to continue using Duo features at the time of extension.
issue