Draft: Store add-ons on offline license upload
What does this MR do and why?
Related issue: https://gitlab.com/gitlab-org/modelops/ai-model-validation-and-research/ai-evaluation/prompt-library/-/issues/333#note_1970340716
Air-gapped customers do not have access to public internet, so they are not able to synchronize add-on purchases using CDot. Let's store this information in the legacy license and create add-ons when the license is uploaded.
Proposal
- Store
duo_pro_seat_count
field in the offline license and use it to createGitlabSubscriptions::AddOnPurchase
with quantity. The field would be similar to code_suggestions_seat_count, but I see that it's used only to indicate that code_suggestions are enabled. Is it discouraged now and we plan to have a better way? - Store
duo_pro_purchase_xid
since it's required forGitlabSubscriptions::AddOnPurchase
or we can generate it somehow - The
expires_on
field of the add-on is equal to expiration date of the license
Edited by Igor Drozdov