Address Mechanizer use case: SaaS NFR "Subscriptions"
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
This use case doesn't directly rely on update_gitlab_plan, but is closely related to the use of it.
The current workflow (hack) involves requesting the partner to start a trial on the namespace, and then a support engineering modifying that Order object manually to change it from a trial to a plan code, setting seat quantity, and extending the end_date (typically for a year)
Why does the use case exist?
SaaS Not For Resale (NFR) subscriptions are not currently supported in GitLab because they don't exist as a product SKU in zuora, and there's no SFDC tracking of the "subscription". We essentially offer them ad-hoc to Partners.
Are there any workarounds?
No.
In the past, namespaces were directly modified via dotcom admin interface to set the plan which circumvents any automation, and occasionally left unregulated, non-expiring Ultimate plans in place.