Add plan name matcher between GitLab and CustomersDot
What does this MR do?
Related to #321364 (closed)
After adding premium and ultimate records to .com (in this MR), a discrepancy between .com and CustomersDot was created: instead of using premium and ultimate, CustomersDot uses the following plan names: premium_saas and ultimate_saas.
When making an API call from the GitLab Billing page for a group that has premium or ultimate plan, this difference will fail to return data from CustomersDot, as these plan names don't quite match between both platforms.
This MR introduces a matcher to take care of these differences.
Screenshots
Just to double-check nothing was broken, I created a new group on my local GitLab then purchased a Premium license.
As expected, the plans record this new subscription is pointing to, is still silver:
More about fixing this in this MR.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because this is developer-facing.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #321364 (closed)